I also use dashes for naming things in CSS. I think it makes your CSS code consistent with the CSS properties (e.g. background-image) But this is just a naming style rule. If your team is happy with naming things using camelCase or underscores go ahead.
On Fri, Feb 11, 2011 at 3:17 PM, Peter van der Zee <[email protected]>wrote: > On Fri, Feb 11, 2011 at 1:57 PM, Trygve Lie <[email protected]> wrote: > > Hi >> >> > Also, I think it's pretty much accepted to use dashes in CSS (rather >> than >> > underscores or camel case). >> >> I would not use that. Dashes has a function in CSS. >> > > I'm sorry, but a dash is a horizontal bar, `-` and it has no special > meaning in css. Never has, and I'm pretty sure it never will. > > On Fri, Feb 11, 2011 at 2:08 PM, Andrew Dodson <[email protected]> > wrote: > > FYI: I dont believe IE6 supports chaining multiple selectors on an element, >> i.e. .foo.bar, the work around for this has often been to create a new >> classname like ".foo_bar"... *pritty orrible ay no* >> > * > * > Correct. Likewise the child selector `>` is not supported by it. And > neither is Array.prototype.map. And... (just saying). Dashes are safe on IE6 > as well. > > I didn't mean to advocate dashes as a best practice or anything, I guess I > missed the minefield warning sign :) > > - peter > > -- > To view archived discussions from the original JSMentors Mailman list: > http://www.mail-archive.com/[email protected]/ > > To search via a non-Google archive, visit here: > http://www.mail-archive.com/[email protected]/ > > To unsubscribe from this group, send email to > [email protected] > -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
