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

Re: ISSUE-3 (monotonic-clock): Animation frame times should be monotonically increasing [Request Animation Frame]

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 23 May 2011 16:15:27 +1200
Message-ID: <BANLkTimVTQege=uodvH3oAiaWuuTf72_kA@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Thu, May 19, 2011 at 12:08 PM, Jatinder Mann <jmann@microsoft.com> wrote:

> As we have been evaluating this spec, the concept of a
> window.animationStartTime property seems like a very reasonable property to
> standardize. This property will allow all animations to have the same
> starting point. Without standardizing this property, web developers will be
> forced to use Date.now(), which currently is not defined as monotonically
> increasing and may not always have a millisecond resolution.
> We feel that both window.animationStartTime and the requestAnimationFrame()
> callback timestamp should be implemented as monotonically increasing clocks,
> in UTC format with millisecond resolution.

Please call it animationTime or even window.currentTime. Then this clock can
be used for other things without major cognitive dissonance.

"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Monday, 23 May 2011 04:15:55 UTC

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