Classic publishing site and X-UA-Compatibility

%3CLINGO-SUB%20id%3D%22lingo-sub-871418%22%20slang%3D%22en-US%22%3EClassic%20publishing%20site%20and%20X-UA-Compatibility%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871418%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20classic%20publishing%20site%20that%20uses%20the%20default%20master%20page%2C%20seattle.aspx.%20%26nbsp%3BIn%20our%20dev%20tenant%2C%20the%20control%2C%20SharePoint%3AIECompatibleMetaTag%2C%20in%20the%20master%20page%20outputs%20a%20tag%20of%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26lt%3Bmeta%20http-equiv%3D%22%22X-UA-Compatible%22%22%20content%3D%22%22IE%3Dedge%22%22%20%2F%26gt%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20in%20the%20prod%20tenant%2C%20it%20outputs%20a%20tag%20of%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26lt%3Bmeta%20http-equiv%3D%22%22X-UA-Compatible%22%22%20content%3D%22%22IE%3D10%22%22%20%2F%26gt%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20explain%20how%20the%20control%2C%20SharePoint%3AIECompatibleMetaTag%2C%20determines%20which%20IE%20compatibility%20mode%20to%20use%3F%26nbsp%3B%20Both%20sites%20are%20configured%20in%20the%20exact%20same%20way.%26nbsp%3B%20We%E2%80%99ve%20also%20checked%20that%20the%20prod%20tenant%20doesn%E2%80%99t%20have%20the%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fdisplay-a-classic-sharepoint-online-site-in-internet-explorer-10-document-mode-4b4572b7-9223-45ec-8497-557a643da12a%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EIE11OptOut%3C%2FA%3E%20site%20collection%20feature%20enabled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20a%20similar%20post%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Developer%2FSharePoint-Online-X-UA-Compatibility-changes-between-tenants%2Fm-p%2F98154%22%20target%3D%22_self%22%3ESharePoint%20Online%20X-UA-Compatibility%20changes%20between%20tenants%3C%2FA%3E%20but%20with%20no%20solution.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

We have a classic publishing site that uses the default master page, seattle.aspx.  In our dev tenant, the control, SharePoint:IECompatibleMetaTag, in the master page outputs a tag of:

 

<meta http-equiv="X-UA-Compatible" content="IE=edge">

 

But in the prod tenant, it outputs a tag of:

 

<meta http-equiv="X-UA-Compatible" content="IE=10">

 

Can anyone explain how the control, SharePoint:IECompatibleMetaTag, determines which IE compatibility mode to use?  Both sites are configured in the exact same way.  We’ve also checked that the prod tenant doesn’t have the IE11OptOut site collection feature enabled.

 

There is a similar post SharePoint Online X-UA-Compatibility changes between tenants but with no solution.

0 Replies