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

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

From: Jatinder Mann <jmann@microsoft.com>
Date: Wed, 9 May 2012 17:50:14 +0000
To: Nat Duca <nduca@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>
CC: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <AE5FFD9402CD4F4785E812F2C9929D6504EEE6A9@SN2PRD0310MB383.namprd03.prod.outlook.com>
> 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.

Received on Wednesday, 9 May 2012 17:52:36 UTC

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