-
Notifications
You must be signed in to change notification settings - Fork 24
Wrong output when mixing selectors #15
Comments
I am going to take a stab at fixing. Will get a chance in about 2 hours. |
The specification does not seem this syntax. But we can think about how to expand it.
|
Oh... In fact I say button a,
.button a, b {} was incorrect but it is not. But the second example with matches is still wrong. button:matches(.is-focused,.is-broken),
.button:matches(.is-focused,.is-broken) {} This way, postcss-selector-matches will be able to do his job. |
What's the final CSS? Like this? button.is-focused,
.button.is-focused, button.is-broken,
.button.is-focused, button.is-focused,
.button.is-broken, button.is-broken,
.button.is-broken {} |
This plugin doesn't need to know since postcss-selector-matches will handle to conversion correctly when this one have done his job correctly ;) (But yes is will look like what you showed) |
Working on it now. That is what it should look like. FYI
the output is currently as follows
I am aiming to produce the following as my expected. Let me know if you have any problems with the output
|
I have a fix, but i would like to try out another solution before opening the PR. |
The last output seems fine. |
This can now be closed. |
gives
Which doesn't seems correct.(edit: it is)This lead to a bug into cssnext where
gives
It's probably because this plugin currently use
.selector
instead of.selectors
when playing with selectors :)Bug reported by @jaredadobe
The text was updated successfully, but these errors were encountered: