X-IE-Version-Freeze

There are a lot of good posts describing problems with IE8′s version selector feature, so I’ll just leave you to read those for some insight into problems that it creates (and how it pushes the IE-compatibility burden off Microsoft and onto other competing browsers in a very impressive way).

They’ve announced what they’re doing in IE8, and as we know from previous conversations with Chris Wilson, they don’t announce until they’re sure:

[W]e have to be very, very careful to be 100% confident when we announce things like “that’s exactly what we’re doing,” or “that’s the date that we are aiming for.” When we don’t, we tend to get a lot of people upset with us, of course, but it’s not just them being upset with us; it’s actually, it can be damaging their business model if they bet on us releasing something in a given timeframe, or bet on us releasing a given feature, and we don’t ship it

So we’re going to see X-UA-Compatible in IE8, with very high likelihood. It’s positioned as something that other browsers could use — if they wanted to ship multiple rendering engines to make download size a further impediment to competing with Microsoft, say, or totally lock themselves out of the mobile market — and the introductory document has examples like “FF=3″ in it.

And we know from the ES4 discussions that Chris believes in different groups working out proposals together, which is why they didn’t make a specific counter-proposal to the one put forward by TG1, after all:

It’s been pointed out that we haven’t made an alternate proposal – well, I’d kinda hoped we could work it out together. “Open to input” should be the way of the web, should it not?

So that makes me wonder: why were no other browser developers involved in this discussion? I guess that would ruin the protective cloak of secrecy, though I don’t know how else people would work things out together. (If Microsoft knows, they’re not telling, but I guess that shouldn’t be surprising?)

The naming of the header is sort of generic, but unless the next big announcement on the IEBlog is the release of IE8′s source code, “render this like IE8 would” really only helps Microsoft, and I think it works against the promising trend of convergence on open standards.

7 comments to “X-IE-Version-Freeze”

  1. Robert O'Callahan
    entered 22 January 2008 @ 4:20 pm

    Actually, I strongly suspect this switch is going to be a bigger burden for the IE team than for us, over time. As I described, it creates a huge burden on IE development, and everyone else will just ignore it.

  2. Alex H
    entered 22 January 2008 @ 5:50 pm

    I actually don’t believe it’s as big of a problem as people make out.

    The doctype switcher has a major issue: it’s a feature of HTML code which turns on/off CSS features. Getting people to obey the HTML standard in terms of mark-up doesn’t do much for their CSS hacks – so getting some idea of the CSS standard they’re using which is independent from their HTML standards-compliance (or not) is a pretty decent idea.

    It’s really just a quirks mode on slight steroids rather than an engine switcher.

  3. entered 22 January 2008 @ 9:31 pm

    I would be very surprised (and disappointed) if any other browsers supported this tag in any way. That would be validating Microsoft’s view of a “versioned” web…

  4. entered 23 January 2008 @ 12:00 pm

    [...] Shaver, Director of Ecosystem Development at Mozilla (Read more) “So we’re going to see X-UA-Compatible in IE8, with very high likelihood. It’s positioned [...]

  5. entered 29 January 2008 @ 1:13 pm

    [...] about IE’s versioning feature. Posted by rsayre Filed in [...]

  6. entered 29 January 2008 @ 1:37 pm
  7. entered 29 January 2008 @ 11:40 pm

    Aside from the exact syntax, MS has been talking about this for awhile. I minuted part of the discussions at the HTMLWG F2F in November, and I got the impression IE’s versioning woes weren’t a new topic with the group.