1 . open IE8
2 . press F12
3 . load msdn.com
you should see
4 . open a new tab and load this site you should see
Please tell me what on the second page triggers the IE8 Compat View IE7 Standards
On the page in question, we do NOT set the X-UA-Compatible meta tag (yet, we are thinking of setting it to EDGE) and we are not sending X-UA-Compatible in the header.
I do not know where in my browser I could set this, I do know that of the three testing this, ONE does not have the issue and the other two do.
Standards mode: Standards mode is called upon to provide support for standardized HTML and CSS in major web browsers. Based on DOCTYPE it will render HTML and CSS.
In Firefox and Opera you can determine if your browser is in "quirks mode" by checking page info. Using document. compatMode , will tell you the mode you are in with most browsers.
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. This feature makes it easier for organizations to use one browser, for legacy web/apps or for a modern web/app.
There are three things which can cause a page to open in IE7 mode:
Browser configuration. This may be an issue particularly for sites on ones local intranet.
The X-UA-Compatible
meta tag.
An X-UA-Compatible
HTTP header.
The browser configuration issue can be overridden by either of the X-UA-Compatible
variants.
If you are sure it's not your browser config, and you can't see a relevant <meta>
tag in the code, then it may be that the X-UA-Compatible
setting is being served as an HTTP header and is being specific in telling the browser to go into IE7 mode.
There's nothing wrong with serving an X-UA-Compatible
setting, but it is more common to set a higher version of IE than a lower one; the lower setting would normally only be used to explicitly downgrade the browser for really old sites.
The browser configuration can be problematic because even if you switch it off on your machine, you can never be sure how other users have their browsers configured. For this reason, it is good practice to serve X-UA-Compatible
either as a meta tag or an HTTP header in most cases.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With