Glen Lipka schrieb:
I hear everyone's points. I think the "easy to remove it in 2012" argument doesn't resonate for me, since anything created today will be changed within 1-3 years (in my experience) and IE6 isn't going away that soon. The screen-reader/mobile stuff seems like they would have a different CSS base than the main browser audience anyway, so wouldn't applicable. The conditional comments are good, but need seperate CSS and limit the option NOT to do that. JS being "required" is a good point, but I guess it depends on how much tweaking versus wholesale changes are used. With our without hacks.
I think, you overlooked the "delivering smaller style sheets to modern browsers argument", which is to me more valid than the "easy to remove" one.
Although I wonder, you were saying that hacks feel dirty, doesn't a style sheet messed up with hacks feel much more dirty than two separate style sheets, of which one is free from hacks?
To avoid overlooking properties that are overruled in IE's bugsheet is just a matter of proper commenting your style sheets.
Last not least I recommend to all using hacks to read 1. Molly about "Long term hack strategies": http://www.informit.com/articles/article.asp?p=170511&rl=1 2. Tantek - inventor of the CSS hack! - about hacks: http://tantek.com/log/2005/11.html -- Klaus
