Contact emails
Spec
http://www.w3.org/TR/css3-animations/
Summary
Support of unprefixed CSS properties for CSS Animations
Motivation
It's pretty obvious but today Blink doesn't support setting unprefixed CSS properties for the animations module. You'll have to use the -webkit-* properties to make your animations work. Supporting the unprefixed counterpart will help the web towards a better place and avoid using proprietary names. With WebKit, Blink is the only major vendor not supporting it.
Compatibility Risk
I believe that the implementation is pretty close to the spec but we need to investigate if parsing and behaviour is aligned. If we intent to change behaviour of the proprietary counterpart (in the name of sharing the code with the unprefixed part) then we potentially could break some sites around. Again based on my experience unprefixing the CSS Transitions (where I changed the behaviour to align with the spec in few cases) it doesn't seem to be an issue. It's a case by case basis that we can discuss on a given patch if the problem arise.
Ongoing technical constraints
It may sounds super easy to do like just aliasing the CSS properties in CSSPropertyNames.in but based on the experience of CSS Transitions (where the original implementation aliased the properties) it is slightly more tricky : property counts in the declared style, prefixed/unprefixed DOM events... Luckily these problems are resolved with the work on CSS Transitions so I expect the implementation to be faster. For the record unprefixed CSS Transitions are shipping since Chrome 26.
Will this feature be supported on all five Blink platforms (Windows, Mac, Linux, Chrome OS and Android)?
Yes.
OWP launch tracking bug?
https://code.google.com/p/chromium/issues/detail?id=234615
Row on feature dashboard?
No. The feature is already in the engine. Should I add a row (and probably one for the CSS Transitions then)?
Requesting approval to ship?
No. I'd like to develop the change in the comfort zone like we did with the transitions properties and let the people experience it with the experimental features. When it's done then I will send an intent to ship.
LGTY?
Thanks.
I think CSS transforms and CSS animations must be unprefixed together at once.Unless you want to end up with this kind of code (which no one does and thus would break the web) -@keyframes bla{15%{-webkit-transform: rotate(30deg);transform: rotate(30deg);}30%{-webkit-transform: rotate(60deg);transform: rotate(30deg);}}
For the record, Firefox and Internet Explorer (and perhaps Opera, not sure) unprefixed all of them (including CSS transitions) at once.
I know of a number of bugs that should be fixed before we ship this. I will mark them as blockers on the tracking bug.