The odd bit

Once is an accident, twice is a coincidence, three times is an enemy action.

The odd bit - Once is an accident, twice is a coincidence, three times is an enemy action.

Microsoft does it again: IE8 and web standards

I thought this was a really early April’s fool when I first read it, but this is all over the place it just has to be true. I picked it up from Robert O’Callahan’s blog. I don’t know who keeps inventing these things, but sometimes you just can’t come up with such funny jokes no matter how hard you try.

Microsoft feels they made a mistake when they changed the behaviour of the “Standards compliant” mode between IE6 and IE7. They argue that web developers had implemented hacks to go around the imperfections of IE6’s standards mode (no kidding, the standards mode really didn’t live up to its name). Then IE7 came and it shipped with improved support for standards. But because of IE detection, IE7 received the same content as IE6 and as such the improved standards mode broke more than it fixed (that says more about the web developer though, I haven’t done a lot of fixes to be IE7-compatible).

So the folks in Redmond believe they should do something. Web pages are developed for a particular browser version and they should never break in a newer browser. It should be rendered by the engine it was created for. Microsoft’s solution? Let’s ship different rendering engines!

<insert awkward silence>

The first thing I can think of is maintenance hell. The second thing I can think of is development hell and the third thing is testing hell. So basically, IE is heading to hell. Small clue for certain readers: typing this paragraph made me think of a certain Peanut. But wait… there’s more from the Redmond Beast!

What if you, as web developer, know a page is compatible with a new IE engine? Just because you know how to do your work shouldn’t leave you with old pages stuck in an old IE version, right? Well, Microsoft agrees and they’ve come up with a way to signal which IE mode you want. You can indicate your page’s compatibility by using a … wait for it … <meta> tag! And it will be a meta tag of the http-equivalent type so you can achieve the same effect by sending an HTTP header via the server.

Is it just me or does Microsoft have a nose for picking the worst solution to solve a problem? Instead of fixing their part, they’re putting the burden on the developers once again. Before IE8 comes out, we can all waste hours/days to add their silly meta tag. This is all for Microsoft’s “Don’t break the web” philosophy. Well hello, Microsoft! You broke it in the first place, fix it without harassing us every time you release a new version of Internet Exploder.

Mind boggling questions sometimes have a really easy and simple answer. How can we make the web a better place? Get rid of IE and leave the web to browsers.

Oh, for the record: this has been made official on the IE Blog.

  • Sandip Saini says:

    I was very much helped by the information with this article. Many thanks at you very fascinating resource.

    4 July 2009 at 10:20

Your email address will not be published. Required fields are marked *

*