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

RE: [Resource Timing] Monotonic Clock

From: Jatinder Mann <jmann@microsoft.com>
Date: Tue, 16 Aug 2011 20:29:18 +0000
To: James Simonsen <simonjam@chromium.org>, public-web-perf <public-web-perf@w3.org>
Message-ID: <EE4C13A1D11CFA49A58343DE361B0B04068EC441@TK5EX14MBXC254.redmond.corp.microsoft.com>
Yes, Navigation Timing needs a similar update. I have gone ahead and updated the Monotonic Clock sections for both Resource Timing and Navigation Timing, like so:

Resource Timing - Section 5.2 Monotonic Clock
The value of the timing attributes must monotonically increase to ensure timing attributes are not skewed by adjustments to the system clock while fetching the resource. The difference between any two chronologically recorded timing attributes must never be negative. For all resources, including subdocument resources, the user agent must record the system clock at the beginning of the root document navigation and define subsequent timing attributes in terms of a monotonic clock measuring time elapsed from the beginning of the navigation.

Navigation Timing - Section 5.3 The Monotonic Clock
The value of the timing attributes must monotonically increase to ensure timing attributes are not skewed by adjustments to the system clock during the navigation. The difference between any two chronologically recorded timing attributes must never be negative. For all navigations, including subdocument navigations, the user agent must record the system clock at the beginning of the root document navigation and define subsequent timing attributes in terms of a monotonic clock measuring time elapsed from the beginning of the navigation.


From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of James Simonsen
Sent: Monday, August 15, 2011 7:14 PM
To: public-web-perf
Subject: Re: [Resource Timing] Monotonic Clock

On Mon, Aug 15, 2011 at 4:52 PM, Jatinder Mann <jmann@microsoft.com<mailto:jmann@microsoft.com>> wrote:
Good point. If you want to create a timeline of the entire page, requiring iframes resources to have the same monotonic clock as the root navigation would be best. I can update the spec to be clear on this point also.

Should we also do the same thing for NavigationTiming within the iframe? It seems like having one reference navigation time that's shared by everything on the page is best for the timeline.

James
Received on Tuesday, 16 August 2011 20:29:48 UTC

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