"Jukka K. Korpela" <
jkor...@cs.tut.fi> writes:
> I wonder why IE 9 was in compatibility mode when you tested. Your page
> starts with <!DOCTYPE html>. Well, there's a blank line before it, and
> it might cause some trouble, but not to IE 9 I guess. I suppose you
> had played with the IE settings (via the "developer tools" in IE?).
There’s a lot of possibilities, e.g. the site might be in Microsoft’s
list of sites that should ne displayed in compatibility view, or the
option ‘Display all websites in Compatibility View’ option might be
checked.
C.f. <
http://msdn.microsoft.com/en-us/library/ff955410%28v=vs.85%29.aspx>
But it is much more plausible that the destroy button, conveniently
located next to the refresh button in the address bar (here’s to good
user interface design), has been accidently used. Happens all the
time, and the list of sites that have been added to compatibility view
is unlikely to ever be discovered and screened for false positives by
average users.
The only way I know (is there another one?) to opt out of the destroy
button as an author (and I think that’s recommendable) is setting the
X-UA-Compatible header(-substitute), which leads to the question which
value to use. The only reasonable one – for this purpose – is ‘IE-Edge’.
Microsoft disagrees:
| Because edge mode documents display webpages using the highest mode
| available to the version of Internet Explorer used to view them, it is
| recommended that you use this document mode for testing purposes
| only. Do not use it for production uses.
<
http://msdn.microsoft.com/en-us/library/cc288325%28v=vs.85%29.aspx>
But then, where did I hear that before?
| In standards-compliant mode, compatibility with other versions of
| Internet Explorer is not guaranteed. When standards-compliant mode is
| switched on, the rendering behavior of documents might differ in future
| versions of Internet Explorer. You should not use this mode for content
| that is fixed in nature, such as content that is stored on a CD.
<
http://msdn.microsoft.com/en-us/library/bb250395%28v=vs.85%29.aspx>
Darn those pesky future versions.