Setting the X-UA-Compatible response header has some aspects I find
remarkable.
meta http-equiv=X-UA-Compatible content=IE=6
or
meta http-equiv=X-UA-Compatible content=IE=5
...
- content=IE=5 or content=IE=6 throws IE8b1 in quirksmode, even if
the document has a standards Doctype.
while
-
So the meta-switch is able to take precedence over the doctype switch in
any case.
Definitely! That's by design.
Doctype switching will continue to work as usual; you can choose
between Quirks (IE5.5) and Standard (IE8). However, any meta switch
will ALWAYS overrule any doctype.
Setting
Ingo Chao wrote:
- content=IE=5 or content=IE=6 throws IE8b1 in quirksmode, even
if the document has a standards Doctype.
The real IE5 and IE6 have many differences in their support and
interpretation of CSS in quirks mode. Does IE8 reflect these differences
- as the meta-number suggests?
So
Gunlaug Sørtun wrote:
Ingo Chao wrote:
- content=IE=5 or content=IE=6 throws IE8b1 in quirksmode, even if
the document has a standards Doctype.
The real IE5 and IE6 have many differences in their support and
interpretation of CSS in quirks mode. Does IE8 reflect these
Based on the Versioning and Internet Explorer Modes whitepaper,
making the assumption that Microsoft just kept the old IE7 Quirks
mode, it seems like we have four modes: IE7 Quirks (versions7), IE7
Standards (version=7), IE8 Standards (version =8) and Best possible
(version=edge), with
