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

Re: requestAnimationFrame time and DOMHighResTimestamp

From: Paul Irish <paul.irish@gmail.com>
Date: Wed, 9 May 2012 17:26:35 -0700
Message-ID: <CAHSVx=-wRhxQOebh61mRF11XhAXN=Toqny6zeS1QXrAz_LAVfQ@mail.gmail.com>
To: James Robinson <jamesr@google.com>
Cc: Jatinder Mann <jmann@microsoft.com>, Nat Duca <nduca@chromium.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Not many developers are using this first parameter, but a few are. I've
talked to a few who picked up on the high res timer and they agree that
it's a better and more useful value to pass. I definitely agree on going
forward with the high res timer as first param.

Depending on performance.now's presence.. I'll likely recommend feature
detecting via:

if (duration < 1e12) /* high res timer */
else /* epoch timestamp */

Chrome Developer Relations
Received on Thursday, 10 May 2012 00:27:35 UTC

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