On 8/6/07, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: > > Currently, Sass will silently eat all but the last selector. Is there > > something I've missed?
> I'm a little torn about this. It seems to me that if you have a CSS > selector that's getting so long it won't fit nicely on one line, the CSS > design needs refactoring. Like for Max's case, I think the proper way to > deal with that /isn't/ to have a huge selector that refers to every > active element; the proper design is to have an "active" class that is > applied to elements that need this style. I've been doing this for years and it's an elegant solution which cuts down on redundant logic in the templates. In Rails apps I apply the controller name as the id, and the action as the class and so detecting the active links/sections is very simple in CSS. > I may be totally wrong, though, so I'll take an informal poll. Hamlites, > how often do you feel the need to have multiline selectors? The only times I've run into this are for the cases already mentioned, highlighting active links and in resetting styles. It's only every now and again, but when it does happen it's unexpected and I do find myself wishing it would work as it does in standard CSS. -- Richard Livsey Head of Agile Development, CitySafe http://citysafe.org http://livsey.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
