Like stated on the selectivzr site "Style sheets MUST be added to the page using a
tag but you can still use @import in your style sheets. Styles defined in

tags won't be parsed." If mothership is the active theme and CSS aggregation is not active, which is usually the case when developing a sub-theme, then all CSS files get loaded by @import

which breaks selectivzr support.

I'm aware that @import is necessary to avoid the IE number of CSS files bug. Probably there's no one line fix but it would be a good idea, to put a note about this right beneath the selectivzr option in mothership.

Comments

mortendk’s picture

hot damn yeah need to look into this for realz thanks for the heads up

mortendk’s picture

im thinking about adding http://www.charlescooke.me.uk/web/lab_notes/ie7_script.html instead though seems to not have the same problems & works right outta the box gotta test it first though 321 times ;)

troyer’s picture

Just keep in mind that some people already build their code on selectivzr. I think mothership needs to stabilize first, so that we all can rely on some core features.

mortendk’s picture

good call

RobW’s picture

+1 for selectivizr, it's a more specific and forward looking solution (and I prefer it :)).

mortendk’s picture

Status: Active » Postponed (maintainer needs more info)

Looks like theres no way to get it to work atm without using the aggregator :(

a dirty work around would be to have a setting that rebuilds the css cache at every page load for development ?

troyer’s picture

I see, well like I said "put a note about this right beneath the selectivzr option in mothership". This way at least everyone is aware of the issue. Maybe with some visual highlighting for the option when CSS aggregation is not active.

mortendk’s picture

Status: Postponed (maintainer needs more info) » Fixed

put in the documentation & in the settings so im closing this one ok ? :)

troyer’s picture

Perfect :)

mortendk’s picture

Status: Fixed » Closed (fixed)

woho