You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's at least one situation where CMQ can change the ordering of rules. Consider the following (we had some SCSS mixins which compiled to essentially this):
CMQ will put both the media query blocks at the end of the file. As a consequence if the screen width >= 100px 'my-class' will be blue. Without CMQ the same screen size would result in green.
This is of course how CMQ is meant to work, but it would be nice to print a warning message in this case. It doesn't look like this would be easy unfortunately, as you would need to trace through the resultant attributes for each select/media query pair and see if anything differed between the original and changed file.
The text was updated successfully, but these errors were encountered:
There's at least one situation where CMQ can change the ordering of rules. Consider the following (we had some SCSS mixins which compiled to essentially this):
CMQ will put both the media query blocks at the end of the file. As a consequence if the screen width >= 100px 'my-class' will be blue. Without CMQ the same screen size would result in green.
This is of course how CMQ is meant to work, but it would be nice to print a warning message in this case. It doesn't look like this would be easy unfortunately, as you would need to trace through the resultant attributes for each select/media query pair and see if anything differed between the original and changed file.
The text was updated successfully, but these errors were encountered: