Add meta tags to PC-side pages: x-ua-compatible META tags

Attentive friends will find the following HTML code more than a < attentive friend will find the following HTML code more than a <meta http-equiv= "x-ua-compatible" content= "Ie=emulateie7"/ > tags!
<meta http-equiv= "Content-type" content= "text/html; charset=gb2312 "/>
<meta http-equiv= "Content-language" content= "gb2312"/>
<meta http-equiv= "x-ua-compatible" content= "Ie=emulateie7"/>
<meta name= "Robots" content= "all"/>
<meta name= "Googlebot" content= "All"/>
<meta name= "description" content= "provide the latest ASP source code, PHP source code,. NET source code, flash source code, website source code, Web source, template, software download"/>
<meta name= "keywords" content= "asp source code, PHP source code,. NET source code, flash source code, website source code, Web source, template, software"/>
<title> Source Download Network-Provide the latest free website source code download </title>
<meta name= "Copyright" content= "www.downhtml.com"/>

        What does this tag mean? Let me take a look at the instructions on MSDN:
        in IE8 Beta 1, which option is the "ie=7" x-ua-compatible tag , which instructs IE8 to display content in IE7 standards mode. However, the scenario this doesn ' t address was when IE=7 was applied as an HTTP header to a site that contains Quirks mode p Ages. The ie=7 HTTP header would force all Pages–both Quirks and standards–to display in IE7 standards mode. Developers using this header while updating their sites would then has to add the ' ie=5 ' <META> tag to each page th EY want to keep in Quirks mode. This logic was fine for many websites. However, if a site has lots of Quirks mode pages, or for the case where pages with frames host a mix of Strict and Quirks Mode Content–as brought to light by IE8 Beta 1 user feedback–the Compatibility opt-out adds a bit more work than we in tended.

     X-ua-compatible is a new setting for IE8, and for browsers other than IE8, this difference differs from content= "ie=7" regardless of whether the page contains <! The doctype> directive, like the standard mode for Windows Internet Explorer 7, is used. and content= "IE=EMULATEIE7" mode follows <! doctype> instructions. For most Web sites, it is the preferred compatibility mode.

Currently IE8 is still in beta, so in order to avoid making the page under IE8 error, it is recommended to directly IE8 using IE7 to render. That is, add the following code directly to the META tag in the header of the page:
<meta http-equiv= "x-ua-compatible" content= "ie=7"/>
So that we can make the page in the IE8 inside the normal performance! http-equiv= "x-ua-compatible" content= "ie=emulateie7"/> Label!
<meta http-equiv= "Content-type" content= "text/html; charset=gb2312 "/>
<meta http-equiv= "Content-language" content= "gb2312"/>
<meta http-equiv= "x-ua-compatible" content= "Ie=emulateie7"/>
<meta name= "Robots" content= "all"/>
<meta name= "Googlebot" content= "All"/>
<meta name= "description" content= "provide the latest ASP source code, PHP source code,. NET source code, flash source code, website source code, Web source, template, software download"/>
<meta name= "keywords" content= "asp source code, PHP source code,. NET source code, flash source code, website source code, Web source, template, software"/>
<title> Source Download Network-Provide the latest free website source code download </title>
<meta name= "Copyright" content= "downhtml.com"/>

What does this label mean? Let me take a look at the instructions on MSDN:

In IE8 Beta 1, then option is the ' ie=7 ' x-ua-compatible tag, which instructs IE8 to display content in IE7 standards mode . However, the scenario this doesn ' t address was when IE=7 was applied as an HTTP header to a site that contains Quirks mode p Ages. The ie=7 HTTP header would force all Pages–both Quirks and standards–to display in IE7 standards mode. Developers using this header while updating their sites would then has to add the ' ie=5 ' tag to each page they want to Ke EP in Quirks mode. This logic was fine for many websites. However, if a site has lots of Quirks mode pages, or for the case where pages with frames host a mix of Strict and Quirks Mode Content–as brought to light by IE8 Beta 1 user feedback–the Compatibility opt-out adds a bit more work than we in tended.

X-ua-compatible is a new setting for IE8, and for browsers other than IE8, this difference with content= "ie=7" is like using Windows Internet Explorer regardless of whether the page contains instructions Standard mode of 7. The content= "IE=EMULATEIE7" mode follows the instructions. For most Web sites, it is the preferred compatibility mode.

Currently IE8 is still in beta, so in order to avoid making the page under IE8 error, it is recommended to directly IE8 using IE7 to render. That is, add the following code directly to the META tag in the header of the page:
<meta http-equiv= "x-ua-compatible" content= "ie=7"/>
So that we can make the page in the IE8 inside the normal performance! http-equiv= "x-ua-compatible" content= "ie=emulateie7"/> Label!

Article to stream code download network ww.downhtml.com reprint please indicate the source.

Add meta tags to PC-side pages: x-ua-compatible META tags