-
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
Merging rem rules sometimes removes pixel fallback, even with compatibility/skip aggressive flags #558
Labels
Comments
@kinglozzer thanks for reporting, I'll take a closer look in the evening - may be a regression from 3.1.x. |
jakubpawlowicz
added a commit
that referenced
this issue
May 3, 2015
We apparently had a `joinAt` in wrong order so adjacent properties were not merged correctly when in compatibility mode.
@kinglozzer It's fixed in 3.2.7. |
👍 thanks @jakubpawlowicz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Take the following example:
cleancss -o test.min.css test.css --compatibility ie8 --skip-agressive-merging
Output is:
Tested on v3.2.6.
The text was updated successfully, but these errors were encountered: