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

Re: Specifying window.performance.now()

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 29 Feb 2012 12:23:46 -0500
Message-ID: <4F4E5F22.3060109@mit.edu>
To: public-web-perf@w3.org
On 2/28/12 7:26 PM, David Mandelin wrote:
> The main application of Performance.now seems to be relative timing, which doesn't particularly require any origin. It seems to me to be a bit easier to allow an arbitrary origin, so that the implementation doesn't have to track a zero time and subtract. Do some important applications require zero to be start of navigation?

The issue is that there are situations where times the browser has to 
pass times to script that should be compared to navigation timing times 
and performance.now() times.  So having a single timebase for all of 
these is a really good idea.

See for example discussion in 
https://bugzilla.mozilla.org/show_bug.cgi?id=453650 about matching other 
timescales to performance.now()

-Boris
Received on Wednesday, 29 February 2012 17:24:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 29 February 2012 17:24:19 GMT