
In a recent post in their official blog the IE team has confirmed that, among other things, the * html selector bug is fixed in IE7’s strict mode. Actually it was mentioned by their lead programmer Chris Wilson before, and this is what he said about it:
As for the * html selector issue — actually, it’s currently fixed (that is, it no longer works) in beta 2; however, I’m on the fence as to whether we should ship that ….
That was more than a month ago. Now, with the plethora of other IE related problems this might seem like a minuscule change they’ve made, but it’s very important for people like me that rely on this bug together with CSS child selectors to work around other IE’s bugs and treat it like a seperate entity from the modern browsers. It would mean trouble in the form of broken sites if they had decided not to fix this in the strict mode, rendering layouts that employ the * html hack incompatible with IE7. Here’s a nice table outlining this dilemma:
IE team’s options
|
* html selector bug |
| Fix |
Ignore |
| Other bugs and CSS |
Fix |
Everything works |
Many sites look broken |
| Ignore |
Many sites look broken |
Everything works |
It looks like, that, unless they don’t care about backwards-compatibility, they will have to fix everything, from rendering bugs to a more complete CSS2.1 support.
One of the stated objectives of the IE team is “to remove all causes of difficulty for web developers”, and I wonder if this marks a small change of attitude from Microsoft. I mean, ASP.NET Whidbey is going to be standards compliant too, MSN search is now valid XHTML, they’re sharing the information about IE7 publicly etc. If it’s true, it means the web will be a better place for all of us, at least for a few years. But if IE remains the market leader, the future of standards like CSS3 is completely in Microsoft’s hands, and I guess that’s the downside of it.