@TheDoc, while you are right that most people does not use underscores in their CSS selectors, it is not merely due to preference. Some older browsers cannot handle the underscores, and thats why that people should avoid using them.
There is one alternative to dashes for word separation, which I’m more fond of. Maybe it is due to my background as a programmer – who knows. I’m talking about camelcase – or just a capital letter to indicate a new word. Some examples:
– page-wrap => pageWrap
– some-long-name-for-a-css-selector => someLongName….
You get the picture.
It doesn’t matter which one you go with. Some might argue that using camelcase is giving you smaller file sizes but that would be nitpicking in my opinion… The most important is what you find easier to read.
When I’m writing css I always name id’s with uppercase first letter (capitalizing each word – tho most of them is single words – examples: #Header, #Footer, #Content, #Menu…). Classes is named in camelcase- examples: .activePage, .fancyHeader, .longStupidClassName… I have not made any decisions on how to do the naming, it is just a de facto standard that has developed through years of work :-)
