W3C home > Mailing lists > Public > public-web-perf@w3.org > July 2011

Re: [RequestAnimationFrame] Processing model defined

From: James Robinson <jamesr@google.com>
Date: Wed, 27 Jul 2011 22:54:56 -0700
Message-ID: <CAD73md+oZd=triPKwGXDLsuNqauL48LXScRuJSkshsaLY_kv_Q@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-web-perf@w3.org
On Wed, Jul 27, 2011 at 8:25 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 7/27/11 11:23 AM, Boris Zbarsky wrote:
>
>> If the animation timeline is progressing, then pages presumably would
>> like to know when the scripted animation should be "done" just like they
>> want to know it for CSS transitions/animations. Right now the only way
>> they can know that is to get a requestAnimationFrame "tick" with a time
>> far enough into the animation, since the browser doesn't actually know
>> when the page considers the animation to be done.
>>
>
> Maybe we should attack the problem from that angle?  Have a way when making
> a requestAnimationFrame call to specify when that animation should be
> considered "done" if the page wants, have jQuery update to do that, and then
> use that information to either do a single tick past the done time or drop
> the callback on the floor entirely once the done time passes?
>
>
How's that different from setTimeout() + canceling the request?


> -Boris
>
Received on Thursday, 28 July 2011 05:55:19 UTC

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