X-UA-Compatible meta tag must be first in the <head> element #146
Conversation
|
Do you have any other references to support your claim? I'm not convinced by that Stackoverflow thread. |
|
I am not happy about it either. We had this issue only with intranet pages where the network team couldn't change the config due to other MS services. IIR old sharepoint was the reason they wouldn't change it. Placing the X-UA-Compatible meta tag first fixed it. <meta http-equiv="x-ua-compatible" content="ie=edge"><!-- if intranet settings force Compatibility View place this first --> |
|
Related: you can't have comments before the X-UA-Compatible meta tag h5bp/html5-boilerplate#1187 Which at one point the HTML5 boilerplate had the conditional comment around the |
|
In general this is really helpful: I tried it now in IE11 and recogniced no difference? (also intranet) |
|
Thank you for the additional references. Although I'd prefer to see something from a respected source, preferably something more recent. Stackoverflow threads and older random blog posts are not the greatest sources. I believe that html comments before the tag will cause issue, but I'm not convinced the current order of the tags is an issue. |
http://stackoverflow.com/questions/6156639/x-ua-compatible-is-set-to-ie-edge-but-it-still-doesnt-stop-compatibility-mode#answer-9624500