W3C home > Mailing lists > Public > public-web-perf@w3.org > October 2013

Re: [ResourceTiming] The clock base to use in ResourceTiming is not defined

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 01 Oct 2013 20:50:01 -0400
Message-ID: <524B6DB9.4090505@mit.edu>
To: Jatinder Mann <jmann@microsoft.com>
CC: "'public-web-perf@w3.org'" <public-web-perf@w3.org>, "Philippe Le Hegaret (plh@w3.org)" <plh@w3.org>, "'arvind@google.com'" <arvind@google.com>, "James Simonsen (simonjam@google.com)" <simonjam@google.com>
On 10/1/13 7:14 PM, Jatinder Mann wrote:
> I think it's reasonable that the terminology section for the Resource Timing, User Timing, and Navigation Timing L2 specs define what they mean by current time, and clarify which definition of time is being used. This clarification is useful specifically since Navigation Timing L1 uses a different definition. I'll take an action to update those specs.

Great, thank you!

> To minimize this confusion, we can clarify the definition in High Resolution Time L2 with text like so:

That sounds good too.

> A duration is just a delta between two time values. Seeing that the DOMHighResTimeStamp definition specifically calls out that it can be a delta of two DOMHighResTimeStamps, and seeing that DOMTimeStamp doesn't have an analogous duration type, I think its fine to not define a separate duration type.

I can live with that, though I still think it's a bit confusing to do it 
that way.  With the other proposed clarifications this will be much less 
of a problem.

-Boris
Received on Wednesday, 2 October 2013 00:50:38 UTC

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