Autoprefixer is removing my trailing semicolons (a remaining rework issue?)

[AndyBean]

Though not technically incorrect, it is a recommended syntax by Google et al to leave the trailing semicolon. I saw on this thread that autoprefixer is built on top of rework, which was was updated over a year ago to return the semicolon; perhaps that update never happened.

It is not a huge deal, both with semicolon and without are considered valid but it is common for application tests to interpret the lack of one as an error, and it annoys my obsessive compulsive self. Should I more appropriately bother the Rework group about this?

-Andrew

[ai]

@AndyBean Autoprefixer has no connection with Rework for a year ;). Autoprefixer is based on PostCSS.

Instead of Rework, PostCSS try to save user code style (indents, trailing semicolon). But maybe there is a regression (we rewrite a lot of parts in PostCSS 3.0 to have the fastest CSS parser).

Can you write some small input with trailing semicolon and output from Autoprefixer without it?

[kyaido]

Hi.

I'm also troubled by this removing semicolons issue.
For example, as to apply the autoprefixer to normalize.css, the code below

html {
  font-family: sans-serif; /* 1 */
  -ms-text-size-adjust: 100%; /* 2 */
  -webkit-text-size-adjust: 100%; /* 2 */
}

after autoprefixer, the code becomes

html {
  font-family: sans-serif; /* 1 */
  -ms-text-size-adjust: 100%; /* 2 */
  -webkit-text-size-adjust: 100% /* 2 */
}

[ai]

@kyaido thanks for example. Now I know, that this problem is with last comment.

I create issue in PostCSS: postcss/postcss#136

[Taritsyn]

Thanks.

[ai]

Fixed in PostCSS 3.0.6.