I agree with those cases. And regarding JS binding to IDs, I shouldn't have
put it that plainly - using classes as selectors in JS certainly makes sense
in many cases.
It's styles like this that drive me crazy!
span.undernav,
div#site-page div.section p.small,
div#page-2 div.other-section h5.class2 {
/*definitions*/
}
Or when someone styles #id-name, then wants to apply those styles on another
page/element, but there is JS functionality bound to that ID. Or when
someone binds JS to a class that is not unique to that one need.
Kevin
--
--
You received this because you are subscribed to the "Design the Web with CSS"
at Google groups.
To post: [email protected]
To unsubscribe: [email protected]