W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2012

Re: Animations (was: [minutes] 2012-10-10 Web Performance WG Teleconference #84)

From: Tab Atkins <tabatkins@google.com>
Date: Fri, 2 Nov 2012 17:38:46 +0100
Message-ID: <CACwK9gd6obsr-GyNAKkKVHKa3kOA1rsWJ8d5qyjY8ZQjeNgYNw@mail.gmail.com>
To: Philippe Le Hegaret <plh@w3.org>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, James Robinson <jamesr@google.com>, public-web-perf@w3.org, David Baron <dbaron@dbaron.org>
On Tue, 2012-10-30 at 13:24 -0400, Boris Zbarsky wrote:
> On 10/30/12 1:16 PM, Philippe Le Hegaret wrote:
> > The bottom line is that the CSS WG is interested in fixing the problem
> > on their side and it will be easy for them to do so.
> Fix in what sense?  Not firing transition/animation events in background
> tabs?
> What about SMIL events?  Same deal?
> Basically, we should get all the web animation APIs on the same page,
> whatever that page is.

Right now the T/A specs are very underdefined about exactly when and
what events are fired.  We figured out that we needed to just define
exactly what events will fire for every transition in the state
machine of an animation.

Once we do so (which will happen soon), Page Visibility or whatever
can just define exactly how the animation state machine is manipulated
in background tabs (for example, pausing the animations upon entering
the background, then scrubbing forward for the duration of the pause
when it's visible again), and what events are fired will just fall out
of that.

Received on Friday, 2 November 2012 16:39:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:33 UTC