Triggering standards mode in Internet Explorer

Recently Microsoft announced that the upcoming Internet Explorer 8 will introduce a special meta element for triggering standards mode. It will look something like this.

<meta http-equiv=”X-UA-Compatible” content=”IE=8″ />

Aaron Gustafson goes into the details in Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8. And almost immediately, the standardistas reached for their pitchforks.

It’s not difficult to understand why. To me, this feels less like a clever solution and more like an exhausted surrender. The web is already littered with broken, invalid sites built around years of Internet Explorer quirks, hacks and questionable decisions. Rather than finally drawing a line in the sand and saying this is how browsers work now, Microsoft appears determined to preserve the whole archaeological dig indefinitely.

Backward compatibility is useful, of course. So is keeping old buildings standing. But at some point you have to stop adding wooden supports and admit that the plumbing is rotten. The strangest part is that most developers probably won’t even know the switch exists. Their sites will quietly fall back to IE7 rendering mode, at which point they’ll stare at the screen wondering why their shiny new IE8 behaves suspiciously like the browser they thought they had just escaped. And somewhere, another conditional stylesheet will be born.

Perhaps this is the unavoidable price Microsoft has to pay for the sins of Internet Explorers past. But it still feels backwards. Standards mode should be the default. If someone desperately needs the old broken behavior, that should require the special switch. Otherwise we’re not moving the web forward. We’re just giving the ghosts a nicer room to haunt.

7 comments

  • avatar
    Martin
    25 Feb, 2008
    Sigh. After having been recently exposed to the entagled mess of writing JavaScript/CSS/XMLHttpRequest applications I'm just getting angry. I can live with the pain of writing for Firefox/Firebug once in a while, but someone should pay for the IE mess. Really.
  • avatar
    Jonas
    25 Feb, 2008
    I've mixed feelings about this, I haven't dived into the debate but I can see why MS has decided on this; given the prerequisites I think this is (probably) the only solution. But it is not the right solution - the prerequisites are wrong, it is time for MS to reap the harvest from ignoring IE for half a decade and pay the price. They've created so very much trouble for so long that they shall not get out of it that easy. The X-UA-Compatible is just a new doctype, so what shall we call the meta tag we need to add when X-UA-Compatible has been abused in the same way as the doctype?
  • avatar
    25 Feb, 2008
    It's a slap in the face to the small group of people who actually care about this kind of thing. It would even be better the other way around, using the element to enforce IE7 rendering if neccessary.
  • avatar
    Jonas
    26 Feb, 2008
    What's even more interesting is that IE8 was announced today (?) as a first beta, IE7 haven't really been out that long, have it!? A high turn around is a good thing, but this fast? Or do they expect a two year development cycle? (I meant half a decade above, off course.)
  • avatar
    26 Feb, 2008
    I heard that IE8 will be demonstrated at MIX08, with a beta release due sometime in the first half of 2008.
  • avatar
    Jonas
    04 Mar, 2008
    The world has been turned <a href="http://www.quirksmode.org/blog/archives/2008/03/ie_team_changes.html" rel="nofollow">upside down</a>.
  • avatar
    04 Mar, 2008
    I saw it this morning and my eyes are still rolling in surprise. Please say it ain't April 1st yet.

Leave a reply