Redundant prefixes in @keyframes

1. Save the following as foo.css:

@keyframes foo {
from { transform: scale(1) }
}

1. Run postcss -u autoprefixer foo.css

2. Outputs:

@-webkit-keyframes foo {
from { -webkit-transform: scale(1); transform: scale(1) }
}
@keyframes foo {
from { -webkit-transform: scale(1); transform: scale(1) }
}

Expected:

@-webkit-keyframes foo {
from { -webkit-transform: scale(1) }
}
@keyframes foo {
from { transform: scale(1) }
}

[Kunepro]

I was bothered by this as well. Would it be possible to add to the README.md the compatibility table for browser that require @-webkit-keyframes { + prefixed properties } @-webkit-keyframes { + unprefixed properties } @keyframes { + prefixed properties } @keyframes { + unprefixed properties } In particular for the ones that don’t fit Kishan’s expected behaviour.

I honestly don’t know what browser versions do require all this extra code, but it might be easier to accept all this overhead if I knew why I’m letting this pass.

If you can do it, thanks.

[Kunepro]

I understand that you are afraid that the prefix gets removed from “transform” (f.e.) before/after @keyframe, and that if we don’t consider all 4 cases we might find ourselves in an unfortunate situation. Thanks for explaining.