I am not sure whether this question has been asked previously or not, but here it is. We know we can set Compatibility mode setting for our site in IIS through HTTP response header like this
X-UA-Compatible IE=<Version>
I have following questions for this:
Which compatibility mode take preference, the one configured with IIS or the other inside Master Page?
Can we put multiple Compatibility setting through IIS? If yes how? Comma separated like this ?
X-UA-Compatible IE=<Version1,Version2>
or mutiple headers like this
X-UA-Compatible IE=<Version1>
X-UA-Compatible IE=<Version2>
or in both ways?
In order:
Another piece of documentation shows how to specify multiple document mode values:
<meta http-equiv="X-UA-Compatible" content="IE=7,9,10" >
Per the previous documentation citation, the highest supported mode specified by the content value wins. With the earlier example:
The docs do provide flowcharts to illustrate this, though these do not appear to be consistent:
The compliance docs provide the most detail regarding document modes (see the child pages in the sidebar), including this handy chart.
The compatibility cookbook also contains a handy chart, but it looks as if it's been mis-identified. It claims to show the decision tree for IE11, however a closer review shows that it more likely shows the decision tree for Enterprise Mode IE (EMIE), an IE11-only mode that emulates IE8 somewhat more faithfully than IE11.
This complexity is a major reason why document modes are no longer supported.
Also, be aware that how you deliver the results also has an impact. If the site is delivered in Intranet zone, you may wish to consider using a Mark of the Web to deploy the site in the Internet zone in order to simplify the documentation mode evaluation process.
Hope this helps...
-- Lance