[HTML] Ie=edge,chrome=1 Meta tags in detail

File compatibility is used to define how IE compiles your Web pages. This file explains file compatibility, how to specify the file compatibility mode for your site, and how to determine which file mode a Web page uses.

The meta-information is often the same sentence:

<content= "ie=edge,chrome=1"  http-equiv= "X-ua-compatible" >

The chrome=1 here is not to say that IE's technology is augmented by the ability to emulate chrome, but rather with Google Chrome frame, the Google embedded browser framework GCF. This plugin can make the user's IE browser look the same, but the user actually uses the chrome kernel when browsing the Web page, and supports Windows XP and the IE6/7/8 of the above system.

The meta tag mentioned above is used to specify that the page is rendered using the chrome kernel after the GCF is installed.

gcf:http://code.google.com/intl/zh-cn/chrome/chromeframe/

Once the installation is complete, if you want to render a page using GCF, just precede the address of the page with GCF: Yes, for example: gcf:http://cooleep.com

But what if you want to specify the page default to use GCF for rendering at development time, and if the GCF is not installed and then rendered using the IE kernel?

is to use this tag.

http-equiv= "X-ua-compatible" This is a special tag for IE8, which is used to specify how Internet Explorer 8 browser simulates the rendering of a particular version of IE, to solve the compatibility problem of IE browser.

For example, specify that the IE8 browser renders the interface using the IE6 rendering method.

Once CSS hacker commonly used to simulate IE7 rendering style code:

< = "x-ua-compatible" = "Ie=emulateie7"/>

The official definition of it:

You can start immediately with open network technologies such as the HTML5 canvas tag, and even include technologies that are not yet supported by Internet Explorer 6, 7, or 8.
Make applications faster and more responsive with JavaScript performance enhancements.
So this code can be interpreted as: If the GCF is installed, use GCF to render the page "" Chrome=1 ", and if no GCF is installed, use the highest version of IE kernel to render" "Ie=edge".

However, the next question comes again, under W3.org's HTML5 verification tool:



A solution, for three major servers, we can configure the HTTP EQUIV rule on the server side:

Apache server, make sure that Mod_headers and mod_setenvif are available, and then in httpd.conf"the new Apache configuration file is apache2.conf" or add the following rule in. htaccess:

<mod_setenvif.c><mod_headers.c>  browsermatch chromeframe gcfheader append x-ua-compatible "chrome=1" ENV=GCF  </ > </  >

For Windows server on IIS7 or later, just modify the Web. config file and add the following information:

<Configuration><system. WebServer><Httpprotocol><customheaders><Addname= "X-ua-compatible"value= "Chrome=1" /></customheaders></Httpprotocol></system.webserver></Configuration>

In the Nginx server, only need to find ginxconf ginx.conf and edit, in the server {} area (preferably a line before the closure) add the following code:

Add_header "X-ua-compatible" "Ie=edge, chrome=1";

[HTML] Ie=edge,chrome=1 Meta tags in detail