IE10 Enterprise Mode document mode selection for legacy intranet applications

Question

IE10 Enterprise Mode Configuration Boundary
IE10 introduced Enterprise Mode as a mechanism to force specific document modes (IE7, IE8, IE9, or IE10) for legacy web applications that require older rendering engines. This feature operates alongside Compatibility View settings and the X-UA-Compatible meta tag, creating a hierarchy of mode selection that can produce ambiguous results when multiple triggers are present.
The documented behavior shows that Enterprise Mode can be activated through Group Policy, the Enterprise Mode Site List Manager, or programmatically via the X-UA-Compatible header. However, the specification does not clearly define the precedence order when a site is simultaneously listed in an Enterprise Mode site list and contains an X-UA-Compatible meta tag declaring a different mode.
Additionally, frame-based applications present a complication where nested frames may inherit or override document modes independently of the parent page's declared mode, potentially causing inconsistent rendering within a single page. The interaction between these mechanisms—particularly when GPO settings, site lists, and meta tags conflict—remains an unresolved decision point for administrators managing legacy applications.
Which mechanism takes precedence when Enterprise Mode is configured through both a site list and an X-UA-Compatible meta tag, and how does frame inheritance affect the final rendered document mode?

Tasadduq Burney · Answer

Document Mode Precedence
When multiple triggers are present, the Enterprise Mode Site List takes precedence over the X-UA-Compatible meta tag. The browser evaluates the site list configuration before it parses the HTML head of the document.

The Full Precedence Hierarchy
To resolve ambiguity in legacy intranet rendering, the browser follows this order of priority (from highest to lowest):

X-UA-Compatible HTTP Response Header: Processed before the document body is read.
Enterprise Mode Site List: Defined via Group Policy (GPO) or the Site List Manager.
X-UA-Compatible Meta Tag: Located within the <head> of the HTML.
Compatibility View Settings: User-defined browser settings.

Frame Inheritance and Rendering
Document mode is evaluated on a per-frame basis. Nested frames do not automatically inherit the Enterprise Mode setting of the parent page if they contain their own valid triggers.

Independent Triggers: If a nested frame has its own X-UA-Compatible meta tag or is listed separately in the Site List, it will render in that specific mode regardless of the parent.
Fallback Behavior: If a frame lacks its own trigger, it may default to the parent's mode or the browser's global default, depending on the specific GPO configuration and IE version.

Verification Steps
To confirm which mechanism is controlling the render, use the following method:

Press F12 to open Developer Tools.
Navigate to the Emulation tab.
Check the Document Mode dropdown to see the active rendering engine.
For frames, select the specific frame from the console's frame dropdown to verify its individual document mode.

Diagnostic Requirement
Are you delivering the X-UA-Compatible instruction via an HTTP header or a meta tag? If using a header, it will override the Site List, changing the recommended resolution path.

IE10 Enterprise Mode document mode selection for legacy intranet applications

IE10 Enterprise Mode Configuration Boundary

1 answer

Document Mode Precedence

The Full Precedence Hierarchy

Frame Inheritance and Rendering

Verification Steps

Diagnostic Requirement

Your perspective belongs here.

0 question comments