你的网站添加X-UA-Compatible meta标签了吗?

王朝网站推广·作者佚名  2011-12-04
窄屏简体版  字體: |||超大  

细心的朋友会发现下面的html代码中多了一个<细心的朋友会发现下面的html代码中多了一个<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />标签!

<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="提供最新的asp源码,php源码,.net源码,flash源码,网站源码,网页源码,模板,软件下载" />

<meta name="keywords" content="asp源码,php源码,.net源码,flash源码,网站源码,网页源码,模板,软件" />

<title>源码下载网 - 提供最新免费网站源码下载</title>

<META name="copyright" content="www.downhtml.com" />

那这个标签是什么意思呢?让我来看下msdn上的说明:

In IE8 Beta 1, that 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 is when IE=7 is applied as an HTTP header to a site that contains Quirks mode pages. The IE=7 HTTP header will force all pages – both Quirks and Standards – to display in IE7 Standards mode. Developers using this header while updating their sites would then have to add the “IE=5” <META> tag to each page they want to keep in Quirks mode. This logic is 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 intended.

X-UA-Compatible是针对ie8新加的一个设置,对于ie8之外的浏览器是不识别的,这个区别与content="IE=7"在无论页面是否包含<!DOCTYPE>指令,都像是使用了 Windows Internet Explorer 7的标准模式。而content="IE=EmulateIE7"模式遵循<!DOCTYPE>指令。对于多数网站来说,它是首选的兼容性模式。

目前IE8尚在测试版中,所以为了避免制作出的页面在IE8下面出现错误,建议直接将IE8使用IE7进行渲染。也就是直接在页面的header的meta标签中加入如下代码:

<meta http-equiv="X-UA-Compatible" content="IE=7" />

这样我们才能使得页面在IE8里面表现正常! http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />标签!

<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="提供最新的asp源码,php源码,.net源码,flash源码,网站源码,网页源码,模板,软件下载" />

<meta name="keywords" content="asp源码,php源码,.net源码,flash源码,网站源码,网页源码,模板,软件" />

<title>源码下载网 - 提供最新免费网站源码下载</title>

<META name="copyright" content="Downhtml.com" />

那这个标签是什么意思呢?让我来看下msdn上的说明:

In IE8 Beta 1, that 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 is when IE=7 is applied as an HTTP header to a site that contains Quirks mode pages. The IE=7 HTTP header will force all pages – both Quirks and Standards – to display in IE7 Standards mode. Developers using this header while updating their sites would then have to add the “IE=5”

tag to each page they want to keep in Quirks mode. This logic is 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 intended.

X-UA-Compatible是针对ie8新加的一个设置,对于ie8之外的浏览器是不识别的,这个区别与content="IE=7"在无论页面是否包含指令,都像是使用了 Windows Internet Explorer 7的标准模式。而content="IE=EmulateIE7"模式遵循指令。对于多数网站来说,它是首选的兼容性模式。

目前IE8尚在测试版中,所以为了避免制作出的页面在IE8下面出现错误,建议直接将IE8使用IE7进行渲染。也就是直接在页面的header的meta标签中加入如下代码:

<meta http-equiv="X-UA-Compatible" content="IE=7" />

这样我们才能使得页面在IE8里面表现正常! http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />标签!

文章来源 源码下载网 ww.downhtml.com 转载请注明出处。

作者E-mail:axin@oneadmin.cn

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
 
 
© 2005- 王朝網路 版權所有 導航