Internet Explorer 8 beta 2 和标准
Internet Explorer 8 破坏了我每查看第三页的内容。 我认为，这个早期版本的目的是让网站所有者有机会更新他们的网站，这样最终版本就不会那么麻烦了。
有人真的这样做过吗？
有人打算这样做吗？
我还没有注意到任何大型网站，如 ebay、myspace、facebook 等，那么为什么小网站如果可以使用兼容模式呢？
我想我会用我的，但是你如何让你的网站兼容 IE7 和 8？
Internet Explorer 8 breaks what must be every 3rd page I look at. The point of this early release was, I presume, to give website owners the chance to update their sites so it wouldn't be such a hassle for the final release.
Has anyone actually done this?
Is anyone even planning on doing this?
I have yet to notice any of the big sites like ebay, myspace, facebook and so on bother so why will smaller sites if they can just use the compatibility mode?
I think i'll do it with mine, but how can you have your site compatible with IE7 and 8?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我开发了一个以兼容IE8为要求的网站，只要我从一开始就在IE8中测试就没有问题。 目前，IE8 的标准与大多数其他符合标准的浏览器非常接近。
如果你不能（或不会）这样做，你通常可以使用一个简单的元标记让你的页面或网站在 IE8 中工作：
它并不总是顺利工作 - IE8 仅在元标记是第一个标记时才注意到它在 head 部分，这与 ASP.NET 主题冲突。 在这种情况下，您可以转而使用服务器范围的更改来写出 HTTP 标头。 我写了关于 此处。
MSDN 有一些关于处理方法的更多信息：
http://msdn.microsoft.com/en-us /library/cc817570(en-us).aspx
I've developed a site with IE8 compatibility as a requirement, and it wasn't a problem as long as I tested in IE8 from the beginning. IE8's standards are very close to most other standards compliant browsers at this point.
If you can't (or won't) do that, you can usually get your page or site working in IE8 with a simple meta tag:
It doesn't always work smoothly - IE8 only notices that meta tag if it's the first tag in the head section, which conflicts with ASP.NET themes. In that case, you can fall back to using server-wide changes to write out the HTTP headers. I wrote about that here.
MSDN has some more information on the ways to handle that:
http://msdn.microsoft.com/en-us/library/cc817570(en-us).aspx
您还可以查看aggiornoexpress for IE8 Compat，它是一个免费工具它会使用 Jon 指向的元标记自动标记您的网站，一旦您的页面在标准模式下正确呈现，它也会删除该标记。
该工具支持 GUI 和命令行，因此可以轻松编写脚本来标记多个站点。 值得一看。
You can also take a look at aggiorno express for IE8 Compat, it is a free tool that automates the tagging of your site with the meta tag Jon points to, it will also remove the flag once u have got ur pages to render correctly under the standards mode.
The tool supports both a GUI and command line so it is easy to script to tag multiple sites. Worth check it out.
我认为此时最安全的选择是选择退出 IE8 渲染； 如果你在页面上使用“IE7模式”标签，即使IE8出来了，它仍然会使用IE7渲染，所以不会给你留下惊喜。
I think the safest bet at this point is to opt out of IE8 rendering; if you use the "IE7 mode" tag on your pages, even when IE8 comes out, it will still use the IE7 rendering, so you won't be left with surprises.
从历史上看，微软的测试版在标准模式下渲染页面方面比浏览器的最终版本更加严格。
这个想法是，在预览阶段，开发人员是唯一关注的人，微软将尝试通过在浏览器上设置更严格的模式默认值来修复他们的网站。 但当向用户发布最终版本时，他们通常会启用兼容模式，使所有从未修复的页面仍然可以工作。
Historically with Microsoft, the betas have been stricter at rendering pages in standards mode than the browsers' final releases.
The idea is that in the preview stage developers are the only ones looking, and MS will try to make them fix their sites by making the stricter mode default on the browser. But when it comes time to release a final version to the users, they generally enable a compatibility mode that makes all the pages that never got fixed still work.
根据 Microsoft IE8 通过 Acid2 测试。 问题可能在于，每个人都已经习惯了 IE7 的问题，以至于他们创建了如此多的 IE 条件解决方法，以至于现在 IE8 越来越接近标准，这些解决方法就失效了。
According to Microsoft IE8 passes the Acid2 test. The problem may be that everyone has been so used to IE7's issues that they've created so many IE conditional workarounds that it breaks now that IE8 is getting closer to the standards.
嗯，标准几乎是一个神话。 没有一个真正的标准。 如果您不相信我，请阅读 Joel 的文章主题。
Well, stadards are pretty much a myth. Ther is no one true standard. If you don't believe me, then just read Joel's article on the subject.