Cool hack, Rafael
I love the way people live in constant fear of Microsoft fixing bugs.
And when their developers eventually do sit down to tackle IE's problems
and release an update, they're not going to tackle any of the crippling
rendering problems and will instead devote their time to removing all
the life-saving compiling methods.
Based on personal experience, I find no real cause for worry.
An ".ie-only" selector is a fantastic little creature that I hadn't seen
before. It has the advantage of being semantic - people will look at
your code and know what's going on.
My alternative is ending your selector with a comma "," which causes
everything apart from IE to ignore the rule. I'd say that in this case
IE performs logically, but (especially if you don't know about it) it's
easily missed and can easily confuse my target audience (other designers
reading through my CSS code).
But whereas the star hack "* html" relies on a bug which remains (it is
often used to compensate for behaviour that IE7 has mostly fixed, so I
hardly think the sites that rely on it are turning in their graves), I
think the two hacks above are not exploiting bugs (I can't imagine
.ie-only being a mistake, somehow).
Regards,
Barney
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
