That tag will try to force the browser to use the latest rendering mode the browser supports. It will not trigger Compatibility mode. Note that the tag has to be the first tag in the head or it will not work. This fact favors using HTTP headers if possible as the order in the HTTP … Read more
TL;DR: The meta tag wins I found the following (updated) flowchart here (link is broken) and associated blog post that provides an explanation of how IE9 determines document mode:
I just had a play and found the following works for me: <meta http-equiv=”X-UA-Compatible” content=”IE=7,IE=9″ > That is with a comma not a semi colon! I haven’t looked at the spec, but the format is similar to content=”IE=7,chrome=1″ that works for Chrome Frame. I also found that content=”IE=7,9″ works but I suspect that is not … Read more
You can use the document compatibility mode to do this, which is what you were trying.. However, thing to note is: It must appear in the Web page’s header (the HEAD section) before all other elements, except for the title element and other meta elements Hope that was the issue.. Also, The X-UA-compatible header is … Read more
I found problems with the two common ways of doing this: Doing this with custom headers (<customHeaders>) in web.config allows different deployments of the same application to have this set differently. I see this as one more thing that can go wrong, so I think it’s better if the application specifies this in code. Also, … Read more
Either X-UA-Compatible is not “standard” HTML (FSVO “standard” that involves appearing on a publicly editable wiki page referenced by the specification) or the Validator isn’t up to date with the current status of that wiki. At the time of writing (20130326) X-UA-Compatible appears on the wiki page under a section that states: “The following proposed … Read more
This is the way to be absolutely certain : <!doctype html> <!– html5 –> <html lang=”en”> <!– lang=”xx” is allowed, but NO xmlns=”http://www.w3.org/1999/xhtml”, lang:xml=””, and so on –> <head> <meta http-equiv=”x-ua-compatible” content=”IE=Edge”/> <!– as the **very** first line just after head–> .. </head> Reason : Whenever IE meets anything that conflicts, it turns back to … Read more
Seem that MSFT has not consider a large intranet environment that we have many different web application running inside. There is no way to bypass the IE8 setting, according to somewhere I read on MSDN forum. So, I will have to beg my system administrators to put some new group policies to change “Compatibility View” … Read more
If you need to override IE’s Compatibility View Settings for intranet sites you can do so in the web.config (IIS7) or through the custom HTTP headers in the web site’s properties (IIS6) and set X-UA-Compatible there. The meta tag doesn’t override IE’s intranet setting in Compatibility View Settings, but if you set it at the … Read more
If you support IE, for versions of Internet Explorer 8 and above, this: <meta http-equiv=”X-UA-Compatible” content=”IE=9; IE=8; IE=7″ /> Forces the browser to render as that particular version’s standards. It is not supported for IE7 and below. If you separate with semi-colon, it sets compatibility levels for different versions. For example: <meta http-equiv=”X-UA-Compatible” content=”IE=7; IE=9″ … Read more