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

Re: Semantics of the time argument on rAF's FrameRequestCallback

From: Yehuda Katz <yehuda.katz@jquery.com>
Date: Wed, 9 May 2012 11:05:18 -0700
Message-ID: <CAMFeDTW1bJEp=O_g9zdmZw__U8uCWX=ZKELJy4Eoy0RkX-rV2A@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: Nat Duca <nduca@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>, "public-web-perf@w3.org" <public-web-perf@w3.org>
What are authors expected to do with this timestamp? What is the use-case?

Yehuda Katz
(ph) 718.877.1325


On Wed, May 9, 2012 at 10:50 AM, Jatinder Mann <jmann@microsoft.com> wrote:

> > In a future rev of rAF, if we ever need to provide *both* begin and
> present time, as CVDisplayLink does,
> > we're going to be in a world of pain if we leave time undefined. The
> only portable way to do such a thing
> > would be to accept a definition of the callback that is of the form
>
>
> We had discussed updating the callback parameter's time value from
> DOMTimeStamp to DOMHighResTimeStamp on the mailing list,
> http://lists.w3.org/Archives/Public/public-web-perf/2012Mar/0017.html. I
> have opened ISSUE-9: Update time value from DOMTimeStamp to
> DOMHighResTimeStamp [Request Animation Frame],
> http://www.w3.org/2010/webperf/track/issues/9, to track making that
> change.
>
> Thanks,
> Jatinder
>
>
>
>
>
Received on Wednesday, 9 May 2012 21:28:19 UTC

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