W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2015

Re: [web-animations] Animation composite order (was: Ordering animations based on when they transition from idle)

From: Kari Pihkala <kari.pihkala@gmail.com>
Date: Thu, 16 Jul 2015 21:26:51 +0300
Message-ID: <CAE0t3My7VKbbiCgnh_XhBTA4tPSAOqZP9mGiYPDKbi4jGKziww@mail.gmail.com>
To: Brian Birtles <bbirtles@mozilla.com>
Cc: "public-fx@w3.org" <public-fx@w3.org>, Shane Stephens <shans@google.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
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 (to emulate the weird behaviour of SMIL).

Could compositeAfter/Before() be insertAfter/Before() or just
.after()/.before()? They would be a bit shorter.


2015-07-16 8:49 GMT+03:00 Brian Birtles <bbirtles@mozilla.com>:
> Hi,
> Just following up on this thread, Shane and I discussed this a bit on
> IRC yesterday and we wonder if we should push ahead with adding the
> ability to tweak priorities soon-ish.
> A few points we discussed:
> * "Priority" may be confused with CSS prioritization. From here on we
>   will refer to "composite order".[1]
> * We want to avoid an API like z-index for setting composite order.
>   See [2] for some extreme examples of how z-index is abused in the
>   wild.
> * An API along the lines of ChildNode[3] using reference nodes is
>   probably better.
>   e.g. animA.compositeAfter(animB);
>   Strawman proposal:
>   Animation.compositeBefore(refAnim)
>     Rewrite sequence numbers so that Animation has the same sequence
>     number as refAnim minus 1. No idea what we should do if either
>     animation is a CSS animation/transition bound to markup. It might
>     throw or we might be able to do something sensible.
>   Animation.compositeBefore(null)
>     Makes this animation the top of the stack.
>   Likewise Animation.compositeAfter (mostly so you can do
>   anim.compositeAfter(null) to put it on the *bottom* of the stack.)
>   A query method might be needed too, e.g. Animation.isBefore().
> With that in mind, I'm ok with using creation-time ordering plus the
> quirk we described for repurposed CSS animations/transitions--namely
> that their sequence number is reset on their first transition from idle
> after being orphaned.
> There's still plenty of work to do to try and align all these
> definitions but what do you think of this approach?
> Best regards,
> Brian
> [1] https://github.com/w3c/web-animations/issues/100
> [2] http://reports.quickleft.com/css
> [3] https://dom.spec.whatwg.org/#interface-childnode
Received on Thursday, 16 July 2015 18:27:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:54 UTC