[Resolved] "Combine CSS" changing priority of CSS cascade?
Thanks for your great caching plugin. It’s the only one that doesn’t break my site, so I really appreciate that.
I’ve been using the CSS combine option with no issues (or so I thought), but I’ve noticed a couple of instances where the cached page renders differently from the original page, due to differences in the CSS cascade.
My theme has a file for custom CSS rules, and I have explicitly loaded this file after all other css files, to ensure that it takes priority over all other stylesheets loaded by the various plugins. However, it seems that when the CSS is combined, the order of files and/or rules is changing, such that my custom css is being overriden by the stylesheet from one of my plugins in the cached version of my pages.
In the original file, the plugin rule is less important than my theme’s rules, so it works as expected, but in the cached version, the order is reversed, and so displays incorrectly.
I can fix this on an issue-by-issue basis, by adding more specificity to my rules, but only if I notice it. A more general fix would be ideal.
I’m not sure exactly how the CSS combine works, so I don’t know exactly why it’s happening, but is this something that you can resolve?
- The topic ‘[Resolved] "Combine CSS" changing priority of CSS cascade?’ is closed to new replies.