-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beautify breaks fancy attribute selectors like ~= #953
Comments
Yup, this is wrong. Fix is coming! |
jakubpawlowicz
added a commit
that referenced
this issue
Jul 8, 2017
Why: * `~` marker can be used both to denote adjacent selectors and inside an attribute matcher.
jakubpawlowicz
added a commit
that referenced
this issue
Jul 8, 2017
Why: * `~` marker can be used both to denote adjacent selectors and inside an attribute matcher.
Fixed in 4.1.6. |
This was referenced Mar 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Input CSS
I love these fancy attribute selectors!
Actual output CSS
Oh.. pumpkins! Note the spaces around the
~
. In decent browsers, well, they'll just roll with the punches and ignore the spaces. But in IE11, it's a syntax error, so the entire rule is ignored.Expected output CSS
Mmm that's the stuff.
Configuration options
The
-O
level doesn't have an effect. This issue seems to entirely be the fault of the beautification. If the beautification is turned off, the output CSS iscd-row>[col~="5th"]{order:5}
, which is correct.Environment
npm ls clean-css
: 4.1.5node -v
: v8.1.0The text was updated successfully, but these errors were encountered: