cFA wrote:
> So let's say I take the route as noted above and I fix the bug by
> using this html:
>
> div id = eventsModule
>
> and the css
>
> #eventsModule - margin bottom 5px
>
> This change has broken backwards compatibility right?
From what you wrote I can't see what backwards compatibility that gets
broken by switching from an "ID + class", to an "ID" on main elements
and "class" on repeated elements approach or a mix of both, as long as
all relevant styles are added to the right IDs and classes and thereby
end up on the right elements.
As long as we keep old IE "combined ID/class" bugs out of the equation,
specificity rules, and how browsers actually handle specificity, haven't
changed much for "author styling" over the last decade. In my experience
the practice of "overstyling" causes most problems, as the author gets
lost in "what applies where". Most solutions would probably work better
with half the amount of styles being better organized.
I may also have gotten lost in in your case somewhere though (happens
all the time :-) ). There are so many ways to "link" HTML/CSS together
through element-targeting and IDs/classes, so it would help to see an
example - site/template - so we can see what you're dealing with.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
