A few weeks back, along with many others in the development community, I wrote in response to Microsoft’s announcement that IE8 would implement version targeting, a means of back-dating a site so that it doesn’t break with new releases of the browser.

While my views expressed in Version Targeting: Defaulting to the Past to Spite the Future? were primarily favorable of the new technique, I expressed my concerns with Microsoft’s decision that IE8 and all other browsers to come would default to rendering as if it were the previous release of the browser if the meta tag, which looks like this:

<meta http-equiv=”X-UA-Compatible” content=”IE=x;FF=x;OtherUA=x” />

was omitted, rather than in the current up to date standards mode. Perhaps the pressure of the masses in the standards community, Microsoft has caved and agreed that the default rendering engine of IE8 will now favor standards compliance rather than giving precedence to the fear of breakage. To quote their March 3rd press release:

Microsoft Corp. is now configuring the settings in Internet Explorer 8, the upcoming version of its browser, to render content — by default — using methods that give top priority to Web standards interoperability.

While their official position is that they have reoriented their company focus away from proprietary winner-take-all competitiveness and toward interoperability, a lot of us (those not so trusting), posit that they most likely just couldn’t stand up to the pressure coming from those aligned with the web standards movement.

Honestly, it doesn’t really matter what contributed most to their decision. Either way you look at it, progressive support for standards is a good thing. In the end, with IE8 now in public beta, it seems the IE team is finally looking forward like the rest of us, instead of shoving their proverbial heads up their own asses. Standards will be supported by default.

Posted on Sunday, March 16th, 2008 at 11:21 pm Follow responses via the RSS 2.0 feed.