IE8 mode supports many established standards, including the W3C Cascading Style Sheets Level 2.1 Specification and the W3C Selectors API it also provides limited support for the W3C Cascading Style Sheets Level 3 Specification (Working Draft) and other emerging standards.IE9 mode provides the highest support available for established and emerging industry standards, including the HTML5 (Working Draft), W3C Cascading Style Sheets Level 3 Specification (Working Draft), Scalable Vector Graphics (SVG) 1.0 Specification, and others.IE10 mode provides the highest support available for established and emerging industry standards, including the HTML5, CSS3 and others.IE11 mode provides the highest support available for established and emerging industry standards, including the HTML5, CSS3 and others.Those same pages would still appear in IE9 mode when viewed with Internet Explorer 9. If a future release of Internet Explorer supported a higher compatibility mode, pages set to edge mode would appear in the highest mode supported by that version. With Internet Explorer 9, this is equivalent to IE9 mode. Edge mode tells Internet Explorer to display content in the highest mode available.Internet Explorer supports a number of document compatibility modes that enable different features and can affect the way content is displayed: To attempt to understand what each means, here are definitions provided by Microsoft: This is a performance hit because the browser must stop and restart analyzing the content. When Internet Explorer encounters the X-UA-Compatible META tag it starts over using the designated version's engine. Internet Explorer begins interpreting markup using the latest version. If you are using the X-UA-Compatible META tag you want to place it as close to the top of the page's HEAD as possible. See the Microsoft Edge note below.Īccording to Microsoft, when using the X-UA-Compatible tag, it should be as high as possible in your document head: Microsoft Edge, the browser that replaced IE11, only honors the X-UA-Compatible meta tag in certain circumstances. IE11 has made changes to these modes see the IE11 note below. The X-UA-Compatible meta tag allows web authors to choose what version of Internet Explorer the page should be rendered as. If you use Twitter Bootstrap and need to eliminate validation warnings, this tag must appear in its specified order. If you only support the latest browsers (IE11 and/or Edge) then I would consider dropping this tag altogether. If you need to support IE9 or IE8, then I would recommend using the tag. This answer was posted several years ago and now the question really should be should you even consider using the X-UA-Compatible tag on your site? with the changes Microsoft has made to its browsers (more on those below).ĭepending upon what Microsoft browsers you support you may not need to continue using the X-UA-Compatible tag. As this answer is now 10+ years old my recommendation would be to leave this tag out altogether, unless you must support old legacy browsers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |