为什么浏览器需要厂商prefixes对CSS3?什么是从刚刚使用标准的CSS3属性阻止他们? [英] Why do browsers need vendor prefixes for CSS3? What is stopping them from just using the standard CSS3 properties?

查看:93
本文介绍了为什么浏览器需要厂商prefixes对CSS3?什么是从刚刚使用标准的CSS3属性阻止他们?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

可能重复:结果
  <一href=\"http://stackoverflow.com/questions/8131846/why-do-browsers-create-vendor-$p$pfixes-for-css-properties\">Why做浏览器对CSS属性来创建厂商prefixes?

例如,如果我有,我想旋转图像,为什么谷歌浏览器一筹莫展的时候,我用变换:旋转(50deg); ,但工作很好,当我使用 -webkit-变换:旋转(50deg);

For example, if I have an image that I'd like to rotate, why does Google Chrome do nothing when I use transform: rotate(50deg); but work fine when I use -webkit-transform: rotate(50deg);?

时不具有标准让这个程序员/设计师只为每个浏览器写入同一code一次,没有一次整点?这是不是就是要在可预见的未来被改变,否则将永远是这个样子?我才刚刚开始使用CSS3,这似乎真的奇怪的我。

Isn't the whole point of having the standard to make it so that a programmer/designer only writes the same code once, and not once for each of the browsers? Is this something that is going to be changed in the foreseeable future or will it always be this way? I'm only just starting to use CSS3 and this seems really bizarre to me.

推荐答案

CSS3还没有一个完整的标准已正式采纳尚未它仍然是一个的建议草案

CSS3 has not been formally adopted as a complete standard yet—it is still a draft proposal.

厂商特定的标签允许开始厂商实施CSS3标准草案CSS3或建议的想法现在使用实验实施,同时确保他们目前与这些专用标记渲染可以在将来从他们的实际CSS3标记为占最终规范的渲染来区分,即使是不同的。

Vendor specific tags allow the vendors to begin to implement CSS3 draft standards or proposed ideas for CSS3 now using experimental implementations, while ensuring that their current rendering with these proprietary tags can be distinguished in the future from their rendering of the actual CSS3 tag as per the final spec, even if that is different.

这篇关于为什么浏览器需要厂商prefixes对CSS3?什么是从刚刚使用标准的CSS3属性阻止他们?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆