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

Re: Specifying window.performance.now()

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 01 Mar 2012 10:31:57 -0500
Message-ID: <4F4F966D.3070301@mit.edu>
To: public-web-perf@w3.org
On 2/28/12 2:47 PM, Jatinder Mann wrote:
> I have uploaded a draft of the High Resolution Time spec here: http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HighResolutionTime/Overview.html. Please review the spec and provide feedback.

"The DOMHighResTimeStamp is a double-precision floating-point number and 
is bound to the double type of ECMAScript." -- the second part doesn't 
make sense.  There is no "double" type in ECMAScript.  Did you mean 
Number?  I don't actually see a need for this entire paragraph, since 
it's all covered in IDL already.  In fact, I'd prefer not having prose 
that duplicates the IDL...

Are there security concerns about subframes being able to extract "now" 
information relative to the navigation start of the root document?

"The difference between any two chronologically recorded time values of 
the now attribute MUST never be negative or zero." -- I'm not sure what 
the "MUST never be zero" requirement means in practice.  If the return 
value is only accurate to 0.1ms, then it seems quite possible to get it 
twice in a row and end up with the same value on modern hardware, but 
the text seems to prohibit that behavior.  Am I missing something?

The rest of this looks just fine.  Thank you for putting it together!

Received on Thursday, 1 March 2012 15:32:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:01:11 UTC