Among the ways to change the compatibility mode for the second page seem promising:
- Via the
X-UA-compatible HTTP header . The web server requested an outdated document mode through an HTTP header. - Via the
X-UA-compatible meta tag . The web page developer used the meta tag to indicate the mode of the outdated document.
The master label metadata of the SharePoint 2010 X-UA-compatible master page, and the meta tag takes precedence over the HTTP header, so this cannot be done at the HTTP level. This leaves us with the second option.
It seems that the first X-UA-compatible meta tag that appears on the page is used by IE (although it is ambiguous in different articles and is not in the MSDN documentation). If you write SharePoint UserControl or WebPart, you can add this code, for example. in Page_Load() to add this header as the first:
HtmlMeta metaEdgeIE = new HtmlMeta(); metaEdgeIE.HttpEquiv = "X-UA-Compatible"; metaEdgeIE.Content = "IE=EDGE"; Page.Header.Controls.AddAt(0, metaEdgeIE);
where HtmlMeta comes from the System.Web.UI.WebControls .
Iterating through Page.Header.Controls you can probably also find and remove the meta tag added by default by SharePoint, although the code above seems sufficient to trigger Edge mode in IE11.
Paweł bulwan
source share