I’ve mentioned my concern over existing hacks and reliance on them may be impacted by the pending release of IE7 before, but now the official IEBlog has posted Call to action: The demise of CSS hacks and broken pages.
Here is a list of common CSS hacks to look out for (please also consider their variations):
- html > body — http://css-discuss.incutio.com/?page=ChildHack
- head:first-child + body — http://centricle.com/ref/css/filters/tests/owen/
- head + body — http://www.dithered.com/css_filters/css_only/head_adjacent_sibling_body.html
- body > element — http://css-discuss.incutio.com/?page=ChildHack
We ask that you please update your pages to not use these CSS hacks. If you want to target IE or bypass IE, you can use conditional comments .
Sure, that’s wonderful, and something that has been looming as a caveat to hack use since the first hack. But the post totally glosses over the reason many pages may now fail if they’ve used these hacks — that MS has fixed some, but not all of their CSS2 support. Just look at the example I used in that past post (happens to be the same one used in the first comment on this latest IEBlog post). If you fix the parsing of selectors, but don’t fix the support for all of the rules that were being hidden then the page you’re viewing is broken because IE7 is broken.
Comments Temporarily(?) Removed