CSS: class vs id behaviour?

IDs and classes are one reason I have issue with Wayfinder and several other snippets using classes for parameters as often times they ought to be IDs. You rarely have two navigation systems on a page with a common class. It makes more sense to have an explicitly identified container so you don’t have problems like fruitwerks. My typical thought is if it will ever only appear on a page once it gets an ID and if it is possibly going to just have contextual differences I use a class.

As with MODx, Web design is easy to learn and hard to master.

I always wrap every unique element in an container with an id and refer to elements and classes within it as #menu ul.nav li (for example) because even though I didn’t know exactly how to calculate the specificity value of each rule (until now - thanks!) I knew that I never had to worry about it if I did that...

I usually do the same thing but many HTML/CSS standards wonks (and sometimes me) like to use as few divs as possible when valid block level containers like UL should suffice.

For the "Offending" snippets, I’ll submit a patch I guess and stop complaining.

Complaints accompanied by suggestions are always helpful. Even just pointing out a potential problem can speed its resolution. As my mom always says: "the squeaky wheel gets the grease".

Haha, thanks for the info, I knew there was something else going on there. I validated my CSS last night and I’m not in the boat you mention, but now I know that something is inherited... just need to look harder.

Thanks!