At least your users can then not decide the render mode using that button. One more good thing about using this meta tag is that the 'compatibilty view' icon is removed from the address bar of the browser. ('Display intranet sites in Compatitiblity View' is not overridable by meta tag or http header - the browser is in complete control of compatibility view in this case)Īlways add this meta tag or an http header? That's a huge issue for many business applications as the programmer CANNOT override this option even with this meta tag. The default for intranet sites in IE8/IE9 is to use compatibility mode. Microsoft considers at least .x to be on a 'Intranet site'. the site is hosted on an 'intranet site' and the default setting for intranet sites is setĬhanging the browsers Compatibility View settings.This article provides an introduction to. This feature makes it easier for organizations to use one browser, for legacy web/apps or for a modern web/app. the browser has been set to always use compatibility mode We created Internet Explorer (IE) mode in Microsoft Edge for organizations that still need Internet Explorer 11 for backward compatibility with existing websites but also need a modern browser.If the browser stills ends up in Compatibility mode when you use a header or the meta tag one of these things is likely the cause: This fact favors using HTTP headers if possible as the order in the HTTP headers does not matter. Note that the tag has to be the first tag in the head or it will not work.

That tag will try to force the browser to use the latest rendering mode the browser supports.

Edge compatibility mode ie 11