- From: Kristopher Giesing <kris.giesing@gmail.com>
- Date: Fri, 4 Sep 2015 14:21:15 -0700
- To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
- Cc: Rachel Nabors <rachelnabors@gmail.com>, "public-fx@w3.org" <public-fx@w3.org>
- Message-ID: <CAAhnRF9e3pcGqwjkY9uoRk3qjz-LB+0xE8iYvr+HbiAS+7pFzw@mail.gmail.com>
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... 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. On Fri, Sep 4, 2015 at 12:34 PM, Amelia Bellamy-Royds < amelia.bellamy.royds@gmail.com> wrote: > I strongly support this. However, I would want to add that it should be > implemented through a consistent document clock interface that affects any > method by which developers may be coordinating animations. > > For context, SVG/SMIL animations have always had a way that you can reset > or pause the overall document clock for animation. I think the plan for > the next level animation elements spec was to extend that to include > changing the playback rate or reversing playback. Although motion on that > spec may have paused, I'd like to see the functionality applied to CSS > animations and WAAPI. > > In addition, the global playback rate should be reflected in the > timestamps passed to request animation frame callback functions, so that > authors can maintain coordination with any other animations that don't fit > in the WAAPI model. > > ABR > > On 4 September 2015 at 13:06, Rachel Nabors <rachelnabors@gmail.com> > wrote: > >> Been seeing a need for a global playback rate for animations. Talking >> with accessibility experts about older users often needing slower >> animations makes me think this is something individual sites if not >> browsers themselves would like to offer user control over. >> >> Currently you'd have to iterate over every animation object and adjust >> their playback rates individually. Seems like a lot of fuss. >> >> I'm told the Web Audio API has a global playback rate you can adjust. Why >> not Web Animations, too? Seems very practical! >> -- >> >
Received on Friday, 4 September 2015 21:21:44 UTC