SharePoint Online X-UA-Compatibility changes between tenants

%3CLINGO-SUB%20id%3D%22lingo-sub-98154%22%20slang%3D%22en-US%22%3ESharePoint%20Online%20X-UA-Compatibility%20changes%20between%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98154%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%20I%26nbsp%3Bhave%20some%20problems%20with%20distinct%20sites.%20The%20new%20seattle.master%20uses%26nbsp%3B%3CIECOMPATIBLEMETATAG%3E%20to%20define%20the%20IE%20version%20for%20the%20SharePoint%20site.%20But%26nbsp%3BI%20have%20some%20tenants%20where%20it%20renders%20compatibility%20to%20IE10%2C%20and%20some%20others%20renders%26nbsp%3Bedge.%20Why%20is%20that%3F%20I'd%20like%20to%26nbsp%3Bforce%20all%20tenants%20to%20go%20edge%20so%20my%20webpart%20works%20fine.%3C%2FIECOMPATIBLEMETATAG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20uploaded%20a%20couple%20pictures%3A%20same%20site%20template%2C%20different%20tenants%2C%20different%26nbsp%3Bdocument%20mode%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98311%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20X-UA-Compatibility%20changes%20between%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98311%22%20slang%3D%22en-US%22%3E%3CP%3ESPFX%20%2B%20React.%20There%20is%20a%20couple%20problems%20with%20Office%20UI%20React%20and%20IE10.%20But%20we%20didn't%20notice%20until%20some%20legacy%20pcs%20started%20accesing%20with%20IE.%20And%20it%20worked%20in%20a%20tenant%2C%20so%20it's%20harder%20to%20explain%20why%20it%20isn't%20working%20for%20just%20those%20clients.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20probably%20modify%20seattle.master%20to%20force%20the%20edge%20tag%2C%20but%20I%20know%20that%20ain't%20no%20good.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98269%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20X-UA-Compatibility%20changes%20between%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98269%22%20slang%3D%22en-US%22%3EHow%20are%20you%20creating%20these%20custom%20WebParts%3F%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello! I have some problems with distinct sites. The new seattle.master uses <SharePoint:IECompatibleMetaTag> to define the IE version for the SharePoint site. But I have some tenants where it renders compatibility to IE10, and some others renders edge. Why is that? I'd like to force all tenants to go edge so my webpart works fine.

 

I uploaded a couple pictures: same site template, different tenants, different document mode :(

2 Replies
How are you creating these custom WebParts?

SPFX + React. There is a couple problems with Office UI React and IE10. But we didn't notice until some legacy pcs started accesing with IE. And it worked in a tenant, so it's harder to explain why it isn't working for just those clients.

 

I'll probably modify seattle.master to force the edge tag, but I know that ain't no good.