Closed alundiak closed 9 years ago
The option works correctly.
http://caniuse.com/#search=keyframes
Firefox doesn't need the prefix for keyframes
since 16, IE since 10 (and there was no support for CSS3 animations before 10), the last Opera on Presto, which is 12.1, also got animations unprefixed. All others including Opera on Blink need -webkit
prefix.
I mean not keyframes itself, but autoprefixer to parse keyframes and replace by custom XYZ-keyframes.
Ok @nDmitry your comment explains everything. Tnx.
The only problem I'm having with keyframes is that it adds prefixed items where they're not needed.
Example:
@-webkit-keyframes string {
0%, 100% {
-webkit-transform: translateY(0);
transform: translateY(0);
}
50% {
-webkit-transform: translateY(20px);
transform: translateY(20px);
}
}
@keyframes string {
0%, 100% {
-webkit-transform: translateY(0);
transform: translateY(0);
}
50% {
-webkit-transform: translateY(20px);
transform: translateY(20px);
}
}
You don't need the prefixed values in the @keyframes and the unprefixed values in the @-webkit-keyframes. Small thing but would be good to optimize.
You do need prefixed values in the @-webkit-keyframes. E.g. Chrome supports unprefixed CSS tranforms, but not animations.
Based on "browsers" setting I expect to have different code (@-o-keyframes, @-moz-keyframes, @-ie-keyframes), but autoprefixer v2.0.0 fails to deliver it, and delivers only @-webkit-keyframes or just standard @keyframes.
I have this settings:
or this
or even this (which I expect to generate all possible variants)
but as result I have only:
When no settings provided - default "browsers", I have only my @keyframnes and nothing new, despite default is this:
I would appreciate any kind of help.