'#' CSS property prefix breaks LESS

[Sam Foster]

In dijit.css there are a few places where we use '#' as a property-name prefix to target IE. This character hasa special meaning in this context for LESS and is tripping up its parser.

Although dijit.css is not currently LESS-ified, we should play nice with LESS wherever we can, and allow folks to lessify this and any other stylesheet as that's the tool we're endorsing.

the '*' character appears to have the same effect of filtering all but IE, and is safe for use with LESS. '_' should also work.

[kiuma]

a less version of claro.css and dijit.css could be made to help runtime testing

[ben hockey]

​http://paulirish.com/2009/browser-specific-css-hacks/ is a good reference for how to target specific browsers with css. it shows that '#' and '*' target ie6 and ie7 whereas '_' only targets ie6. so, substituting '*' for '#' should work.

[bill]

Hmm, I could change the # to * but I don't see what practical value this would have. Why would people run dijit.css through LESS when dijit.css doesn't have any less directives?

[kiuma]

Replying to bill:

Hmm, I could change the # to * but I don't see what practical value this would have. Why would people run dijit.css through LESS when dijit.css doesn't have any less directives?

Ok I admit that dijit.less is not of very practical use, but for a claro.less is still an option because it gives the possibility to use less.js client side with all its advantages for testing during development.

[bill]

OK, but isn't claro already in less format?

[bill]

patch to dijit.css, needs testing (on IE especially)

[bill]

Going to close this for now. I don't see any practical reason to change dijit.css.