Browser hacks such as these are considered to be very bad. What if one browser fixes the bug that allows this stuff to be detected, but not the bugs you're hacking for?
I think the best solution is to write a site that works in all reasonable (non-IE) browsers, and use conditional comments to fix IE's idiosyncrasies. - Nathan weepy wrote: > i've thought of this before, where often i'll do : > > margin: 10px > *margin: 12px > _margin: 14px > > first is seen by FF, IE6 and IE7 > second is seen by FF > third is seen by FF and IE7 > > the problem about putting them in under the umbrella of a browser is > that I'm not sure that they are well defined enough. Ie - do they > always work ? ? For something to go into HAML core they really need > to be rock solid. > > Perhaps someone that knows more about Xbrowser CSS could flesh this > out more ? > > > > On Jul 19, 4:58 pm, IvanK <[EMAIL PROTECTED]> wrote: > >> I've had a thought - you know of the holy hack and the underscore hack >> right? well, why can't we do something similar in sass, but rendering >> valid css in the process - so, when you have something like >> >> #sidebar >> :margin-left 2em >> :overflow hidden >> :ie6 >> :height 1px >> >> it'll render mycss_ie6.css, with only the contents of the :ie6 >> selector, thus you will end up with a lot more readable css, while >> still keeping it hack-free... >> (you can include those sheets with the ie's conditional comments or >> use javascript detection) >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
