X-UA-Compatible meta tag needed for intranet environments to ensure Portal's browser support.

Description

NOTE: This ticket depends on AUI-817*, to function properly.*

As a Portal developer, in an intranet environment, I need IE 8 & 9 to behave in a consistent manor, regardless of my group policy settings.

To ensure consistent behavior, IE needs a special meta tag to be present in the <head> of the request.

Note: We will be using 9 as it is the highest current version we test with.

Should this be a portal.properties setting? To allow for easy environment customization.

References:
http://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx
http://blogs.msdn.com/b/ie/archive/2008/08/27/introducing-compatibility-view.aspx
http://stackoverflow.com/a/9624500/218161
http://msdn.microsoft.com/en-us/library/cc817574.aspx
http://blogs.msdn.com/b/ie/archive/2009/02/16/just-the-facts-recap-of-compatibility-view.aspx

Environment

Tomcat 7 + HSQL. Portal 6.2.x GIT ID: 35cd0f79c729ad527ac71f3c18e4b0102dc9deb8 Tomcat 7 + HSQL. Portal 6.1.x EE GIT ID: bf94fddd8d4cd00bd87d2057631239d9062d73fa IE 8, 9

Linked issues

causes

LPSA-20690

Navigation menu of classic theme has z-Index and mousemove problems in Internet Explorer 8 after upgrading to 6.1.1 CE GA2

Patrick Armitage

is caused by

AUI-817

UA.selectors and UA.ie reports improper version in IE when X-UA-Compatible meta tag/HTTP header is used in an intranet environment.

Nate Cavanaugh

is related to

LPSA-37683

Correct IE Compatibility View in BrowserSnifferUtil

Brian Chan

relates

LPSA-27954

Add Images Link in web content requires click and drag in order to Image Properties window to display.

Jonathan Mak

LPE-8389

X-UA-Compatible meta tag needed for intranet environments to ensure Portal's browser support

Bryan Engler

LPSA-23346

Tag selector not labeled properly

Luyang Tan

Activity

Show:

Sophia.Zhang March 20, 2013 at 2:33 AM

Passed Manual testing due to closed ticket using this software upgrade.

Byran Zaugg February 4, 2013 at 4:12 PM

This ticket depends on , to function properly.

Byran Zaugg February 4, 2013 at 9:23 AM

One other option, we may have, is to adjust how AUI identifies IE7 and IE8 in Compatibility Mode. I will research if this is feasible.

Byran Zaugg February 4, 2013 at 9:19 AM

Microsoft says, in many places, that setting the HTTP header or placing the <meta> in the <head> will allow the page to render in Standards Mode, without triggering Compatibility Mode.

But every attempt to do this, as well as many comments online to the contrary, convinces me that this is not the case.

It appears the only way to prevent Compatibility Mode, triggering on an intranet, is the disable it via Compatibility Mode Settings in IE directly or via Group Policy.

http://blogs.msdn.com/b/askie/archive/2009/03/23/understanding-compatibility-modes-in-internet-explorer-8.aspx#10067607
http://www.armedia.com/blog/2011/05/display-intranet-sites-in-compatibility-view-or-wtf-happened-to-my-webapp/