I know css inside and out, and your hack makes sense! If ‘valid’ css does not work across browsers then who cares about W3C standards. Less conditional statements (messy) and no need for a separate stylesheet. Web clients don’t care about css validation, users don’t care about css validation, and microsoft sure as hell don’t care…doing more work just teaches IE to be even more lavy than it already is with regards to adhereing to web browser recommendations.

And I need to know this css will work in upper version in IE ?

Actually, the coder needs to study the most common IE bugs and learn how to approach them reasonably. I did this once, in one of my first CSS-based projects. Since then I not only solve IE issues in seconds, but I also understand how every rule I defined works. It’s as simple as that.

It frankly surprised me that these legacy techniques were received with such popularity nowadays. They were adopted by many people four years ago, but it’s really difficult to find recent forum threads with these kind of antidotes.

Also, it’s worth mentioning that IE6 will probably die in the next six months. I advise you guys to look at your analytics data and watch the trend. I’m working in a project that – in Brazil, a 3rd world country – will likely to have less than 4% of IE6 market share by October this year.

My point is that conditional comments permits modern and clean code, with the ease of just trash one line of code in the next few months, when IE6 and IE7 will be irrelevant for most projects.

Hope we all make efforts to write more and more clear and smart code.

Cheers!