IE=edge

After reading the article on ala about IE8 I have to say I think that despite their insistence that the  IE=edge flag should not generally be used I think it is the solution for most developers. If you code to the standard you shouldn’t cripple your site by targeting an obsolete browser. The whole point of web standards is that a new browser, if it follows the standard, will not break your layout.

However, I don’t think the meta tag is a necessarily bad idea. I think most developers working on consumer-facing apps should avoid it. But there is a good reason to use it: intranets and other custom web applications. These are apps that are business critical, but delivered in an environment where IT can make requirements so that users can access internal apps. Providing a way of targeting a specific browser version makes sure that those apps don’t break when users upgrade their browsers.

I would hope that this will actually encourage more IT departments to speed deployment of IE8 if they can be sure it won’t break access to mission critical internal tools. This is great for us, the developers of the consumer web, because we can target our apps to the standard without fear of users stuck in ancient browsers just so they can use Peoplesoft. 

One Response to “IE=edge”

  1. Sean Benoit Says:

    I completely agree with this point of view. Most articles I’ve seen about the MS desire to create yet another meta tag results in flaming without seeing the big benefit of this - which you’ve pointed out so nicely - corporate use.

Leave a Reply