The issue with this technique is that several of the most common techniques for handling IE bugs aren't even valid CSS. The notable examples that come to mind are the opacity filter method for transparent PNG support and the behavior file required for generic :hover support (both in IE6).
Given that probably 90% of the UA-specific CSS tweaking is for IE, doesn't it make sense to serve it using the method IE itself recommends (conditional comments)? Adding classes via jQuery works great until you turn of JS, while the recommended method will always work. Note that most of the other browsers that used to be targeted by hacks are either obsolete (old versions of Netscape) or impossible to support (eg, IE5 on Mac b0rks Rails session cookies). --Matt Jones -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
