In my own personal opinion, if you get into the situation where you want
to use a selector like:
.class1.class2 { stuff }
then it is time to do a little re-factoring. The whole point of allowing
an element to have two or more classes is so that each class remains
semantically logical. As you pointed out, it is legal to use a selector
like the above, but I would never allow such code on any project I was
working on. Worst case is you need to be more specific with your rules.
Obviously, the cascade determines exactly which rule will win, but I
would also be very wary of relying on source-order - it would be far too
easy for you (or someone else) to decide to tidy up the stylesheet at
some point and change the order of these two rules.
Mike
Mike Brockington
Web Development Specialist
www.calcResult.com
www.stephanieBlakey.me.uk
www.edinburgh.gov.uk
This message does not reflect the opinions of any entity other than the
author alone.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************
