Confusing `raws` behaviour

Ref: December 23, 2016 10:11 AM

    --layout-around-aligned: {
      -ms-flex-line-pack: distribute;  /* IE10 */
      -ms-align-content: space-around;
      -webkit-align-content: space-around;
      align-content: space-around;
    };

    /*******************************
              Other Layout
    *******************************/

    --layout-block: {
      display: block;
    };

I looked into the AST produced by PostCSS and what ends up happening is that the semicolon from (logically) the first rule is in fact tacked on to the before raw value of the comment node. Because cssnano removes the comment nodes then the semicolon is lost, but I don’t think that the semicolon being part of the comment node is correct.

[ai]

Done a1cf3e7

I added rule.raws.ownSemicolon with ";" or "[any spaces];" content.

There is only one problem with current implementation. If we will have comments between } and ;, parser will not consider, that semicolon is part of rule.

But this limit is very rare and I will fix it if @apply because a really standard.

[zliebersbach]

Thanks, looking forward to it. If you need some testing done, just let me know. 😉