W3C home > Mailing lists > Public > public-web-perf@w3.org > April 2015

RE: [RequestAnimationFrame] clarification of what 'time' is

From: Todd Reifsteck <toddreif@microsoft.com>
Date: Wed, 15 Apr 2015 07:17:42 +0000
To: Michael Blain <mpb@chromium.org>, Jerry Jongerius <jerryj@duckware.com>
CC: public-web-perf <public-web-perf@w3.org>, Justin Rogers <justrog@microsoft.com>, Tobin Titus <tobint@microsoft.com>
Message-ID: <BN1PR0301MB0612A9611B274A920DDD1FD2C2E50@BN1PR0301MB0612.namprd03.prod.outlook.com>
Could you quickly explain the scenario that this update would improve?


From: Michael Blain [mailto:mpb@chromium.org]
Sent: Tuesday, April 14, 2015 1:58 PM
To: Jerry Jongerius
Cc: public-web-perf
Subject: Re: [RequestAnimationFrame] clarification of what 'time' is

That's a good option to allow. Do you think you can suggest a change in https://docs.google.com/document/d/1SukXPZVUmDb8srqzAGI6Muu55aue9UUhY6XC4SFQFBs/edit?usp=sharing

to that effect, if it looks good to folks I can merge it in.


On Tue, Apr 14, 2015 at 10:29 AM, Jerry Jongerius <jerryj@duckware.com<mailto:jerryj@duckware.com>> wrote:
The 'time' in the rAF callback (Processing Model) should be altered in the
spec to allow (encourage) a web browser to pass the known begin time of the
frame (the vsync timebase) as the 'time', rather than performance.now().

Received on Wednesday, 15 April 2015 07:18:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 15 April 2015 07:18:12 UTC