2015-06-22 7:27 GMT+03:00 Amelia Bellamy-Royds :
> Keywords also complicate the animatability of the property. And since this
> property is all about animation, that should be a significant factor.
You could simplify animatability even further by removing the angle
from motion-rotation. It can be
2015-06-22 9:47 GMT+03:00 Shane Stephens :
> I think this is so that you *can* move the motion path if you need to. If
> motion came first then you'd need to resort to nested divs or similar.
I think the translate, rotate, and scale properties were designed to
help authors to write the most common
2015-07-15 9:04 GMT+03:00 Shane Stephens :
>> > This is
>> > slightly better than start time ordering, but not much - for example, it
>> > means that if you've started other animations in the wrong order with
>> > respect to the animation you're about to start, you are out of luck
>> > unless you
I like the proposal! After this, there isn’t really any need for a
separate “priority”/“composite order" property (in web animations
level 2 spec). If someone needs it, it can be written as a javascript
library. It is also possible to write a JS library to order by start
delay or some other value (
>> Out of curiosity, do we even need the notion of sequence numbers? Or can
>> animations be regarded as belonging to a list or array structure that
>> can be enumerated and manipulated with familiar push/pop/insert/append
>> APIs? (Apologies if this has been discussed before.)
>
> I think sequence
