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

Re: requestAnimationFrame time and DOMHighResTimestamp

From: James Robinson <jamesr@google.com>
Date: Fri, 11 May 2012 12:22:46 -0700
Message-ID: <CAD73mdKQg_ntwH5-wy3yHUjGb5naAwg7mC=S_noOyPe2A95Yvg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-web-perf@w3.org, "Robert O'Callahan" <roc@ocallahan.org>
On Fri, May 11, 2012 at 12:17 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 5/11/12 1:21 PM, Jatinder Mann wrote:
>> I've made this change in 458:4843fb42912f along with defining that the
>>> callback's parameter is gathered
>>> by running the window.performance.now() algorithm before any callbacks
>>> are invoked.
> This is likely to be what Firefox ends up shipping in the near term, but
> it's not clear to me that this is the right long-term behavior.
> Robert, do you have any thoughts on this?  The thread, if you haven't been
> following, is about the value passed to the requestAnimationFrame callback.

My current thinking is that if we want to pass a present time (emphasis on
the second syllable) it'll be a second parameter to the callback. I'm open
to suggestion on this point, however.

- James

> -Boris
Received on Friday, 11 May 2012 19:23:15 UTC

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