http://blog.csdn.net/wyx100/article/details/50450728
1、Mozilla内核
[css]
元素选择器{-moz-transition:运动的样式 持续时间 运动形式 延迟时间;}
2、Webkit内核
[css]
元素选择器{-webkit-transition:运动的样式 持续时间 运动形式 延迟时间;}
3、Opera内核
[css]
元素选择器{-o-transition:运动的样式 持续时间 运动形式 延迟时间;}
4、W3C 标准
[css]
元素选择器{transition:运动的样式 持续时间 运动形式 延迟时间;}
-ms-transform:rotate(7deg); //-ms代表ie内核识别码
-moz-transform:rotate(7deg); //-moz代表火狐内核识别码
-webkit-transform:rotate(7deg); //-webkit代表谷歌内核识别码
-o-transform:rotate(7deg); //-o代表欧朋【opera】内核识别码
transform:rotate(7deg); //统一标识语句。。。最好这句话也写下去，符合w3c标准
What is WebKit and how is it related to CSS?
解答1
Update: So apparently, WebKit is a HTML/CSS web browser rendering engine for Safari/Chrome. Are there such engines for IE/Opera/Firefox and what are the differences, pros and cons of using one over the other? Can I use WebKit features in Firefox for example?
Every browser is backed by a rendering engine to draw the HTML/CSS web page.
IE → Trident(discontinued)- Edge → EdgeHTML (clean-up fork of Trident)
- Firefox → Gecko
Opera → Presto(no longer uses Presto since Feb 2013, consider Opera = Chrome nowadays)- Safari → WebKit
- Chrome → Blink (a fork of WebKit).
See Comparison of web browser engines for a list of comparisons in different areas.
The ultimate question... is WebKit supported by IE?
Not natively.
解答2
Addition to what @KennyTM said:
- IE
- Engine: Trident
- CSS-prefix:
-ms
- Edge
- Firefox
- Engine: Gecko
- CSS-prefix:
-moz
- Opera
- Safari
- Engine: WebKit
- CSS-prefix:
-webkit
- Chrome
1) On February 12 2013 Opera (version 15+) announces they moving away from their own engine Presto to WebKit named Blink.
2) On April 3 2013 Google (Chrome version 28+) announces they are going to use the WebKit-based Blink engine.
3) On December 6 2018 Microsoft (preview build ready in early 2019) announces they are going to use the WebKit-based Blink engine.