On 4/5/07, Howard Jones <[EMAIL PROTECTED]> wrote:
Mobile users? Some Screen-readers (i.e blind or partially-sighted users)? Companies who (rightly or wrongly) have a policy of not allowing 'active' content? Various robots/screen-scrapers?
We might have gotten off-topic. My fault for straying actually. Your point is well taken however. *The original topic was CSS hacks and how jQuery could alleviate the need.* Options I have read here are: 1. Server-side to put the class in the body. (Pro- no need for JS) 2. Conditional comments for seperate CSS. (Pro- easy to remove when IE6 dies (2012?) 3. CSS Hacks in seperate or not css (Pro - no need for JS or server-side) 4. jQuery to put class in the body (Pro - dont need to ask an engineer to help you and no "hacks") 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. And of course, now I gotta bike to work. If only jQuery could be set up to read my mind and post the thoughts here remotely. Maybe in v2.0. G
