Amen to that, JIMD. !important easily eliminates spaghetti problems,
with 3rd-party components. (Although, i would counter that CSS applied
judiciously, ESPECIALLY to very large sites, can vastly reduce the
effort to apply global formats site-wide. But some CSS-fanatics say
"never, ever use inline-styling", which is fanatical.)
UWE, using unique identifiers in the candy is not enough to isolate
candy-html from your site-css:
-unique identifiers mean that the candy-css will only affect the
candy html, and not the rest of your site. that's a GOOD thing.
-but your site-css, most-likely NOT using identifiers or classes
in many places, will ALSO affect the candy-html, messing up the candy.
BAD thing. RICARDO, I would not call this "bad coding"-- the main-site
css rightfully assumes that it is the god-css for your site, so it
should not have to bother with any kind of "class=MyWebsite" on every
tag. But this does put the burden on the candy to insulate itself from
the site-css. The combination of unique id's, classes, and !important
does the trick.
