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

Re: [web animations] Global playback rate

From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Date: Fri, 4 Sep 2015 15:53:36 -0600
Message-ID: <CAFDDJ7zVUvcFDqrAtreydFQSoxmYcjDh8SC1XesnevrtgtNqdQ@mail.gmail.com>
To: Kristopher Giesing <kris.giesing@gmail.com>
Cc: Rachel Nabors <rachelnabors@gmail.com>, "public-fx@w3.org" <public-fx@w3.org>
(comments below)

On 4 September 2015 at 15:21, Kristopher Giesing <kris.giesing@gmail.com>
wrote:

> Are you suggesting that this global animation clock scaling would also
> affect the interpretation of values passed to setTimeout (which is also
> sometimes used to control animations)?  That seems like it might be going a
> bit far...
>

Too far, I agree.  For request animation frame, I wasn't suggesting that
you change how frequently the callback is run, only change the parameter it
receives.  The author would decide whether and how to use it.


> As an alternative, the global animation clock could be exposed as one of
> several clocks, with APIs for converting values between clocks with
> different rates. That might add a lot of API though.
>

I don't know that you need multiple clocks, just access to the main
animation clock.  For example, the SVG/SMIL clock's current time can always
be retrieved from the SVG element.  Authors already have access to the
system clock through core JS functions.  It would still tick away as normal.

That said, the full SMIL model (never implemented in SVG) does include the
concept of nested "time containers", each of which can be paused, sped up
or slowed down, but which also inherit changes to their parent's flow of
time.  The main use is for syncing parts of an animation with audio, video,
etc., which might be paused without pausing everything in the document.
It's a something to keep in mind for future extensions.

~ABR
Received on Friday, 4 September 2015 21:54:04 UTC

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