Comments on: X-IE-Version-Freeze

By: fantasai

fantasai — Wed, 30 Jan 2008 04:40:04 +0000

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.

By: Robert Sayre: Strategy For Dealing With IE’s version selection

Robert Sayre: Strategy For Dealing With IE’s version selection — Tue, 29 Jan 2008 18:37:59 +0000

[...] More about IE’s versioning feature.http://blog.mozilla.com/rob-sayre/2008/01/29/strategy-for-dealing-with-ies-version-selection/  [...]

By: Open Rob Sayre’s Open Mozilla Open Blog » Blog Archive » Strategy For Dealing With IE’s version selection

Tue, 29 Jan 2008 18:13:34 +0000

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

By: Opera, Mozilla and Safari react to IE’s solution for browser compatibility issues

Wed, 23 Jan 2008 17:00:35 +0000

[...] 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 [...]

By: Jeff Schiller

Jeff Schiller — Wed, 23 Jan 2008 02:31:32 +0000

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…

By: Alex H

Alex H — Tue, 22 Jan 2008 22:50:59 +0000

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.

By: Robert O'Callahan

Robert O'Callahan — Tue, 22 Jan 2008 21:20:29 +0000

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.