Google 字体 API 生成 CSS 2.1 验证错误
使用 Google Font API 的页面将作为 CSS3 进行验证，但不会作为 CSS2.1 进行验证。这是直接来自 Google 说明的 href：
<link href="http://fonts.googleapis.com/css?family=Yanone+Kaffeesatz" rel="stylesheet" type="text/css" id="googlefont" />
CSS 2.1 和 XHTML 1.0 Strict 具有不合理的限制，因此当没有可行的解决方案（即嵌入 Flash 视频，即没有其他交叉方法）时，我并不反对脚本解决方法-浏览器，据我所知，易于实施的解决方案）。
是否有可行的解决方案，如果没有，有人可以建议脚本解决方法吗？或者我应该只验证 CSS3 并称其为良好？
Pages using the Google Font API validate as CSS3, but not as CSS2.1. Here is the href, straight out of the Google instructions:
<link href="http://fonts.googleapis.com/css?family=Yanone+Kaffeesatz" rel="stylesheet" type="text/css" id="googlefont" />
CSS 2.1 and XHTML 1.0 Strict are unreasonably restrictive, so I'm not against scripting workarounds when there is no workable solution (i.e. for embedding Flash video, that is, there's no other cross-browser, easily implementable solution that I know of).
Is there a workable solution, and if not, can anyone suggest a script workaround? Or should I just validate as CSS3 and call it good?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
为什么它不能通过 CSS2.1 验证，这不是很明显吗？
Google Font API 使用的是
@font-face，它不是 CSS 2.1。@font-face目前包含在 CSS 级别中3 工作草案，以及现已弃用的 CSS 2 文档中的还有。如果您根据这两个规范（但不是 CSS 2.1）检查它，它将进行验证。Isn't it obvious why that doesn't validate as CSS2.1?
Google Font API is using
@font-face, which isn't CSS 2.1.@font-faceis currently included in the CSS Level 3 Working Draft, and also in the now deprecated CSS 2 documents. It will validate if you check it against both of these specifications, but not CSS 2.1.这是一篇有趣的文章，解释了为什么验证并不是一切。确保不存在诸如孤立标签之类的错误是件好事。实际上，如果它是有效的 CSS3 并且在 CSS2.1 中不验证，则不会有任何问题。
http://www.codinghorror.com/blog /2009/03/html-validation-does-it-matter.html
Here is an interesting article explaining why validation isn't everything. It's nice to do to be sure there no mistakes like orphaned tags. In reality there won't be any problems if it is valid CSS3 and doesn't validate in CSS2.1.
http://www.codinghorror.com/blog/2009/03/html-validation-does-it-matter.html