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

RE: [Resource Timing] Monotonic Clock

From: Jatinder Mann <jmann@microsoft.com>
Date: Mon, 15 Aug 2011 23:52:30 +0000
To: James Simonsen <simonjam@chromium.org>, public-web-perf <public-web-perf@w3.org>
Message-ID: <EE4C13A1D11CFA49A58343DE361B0B04068EBC79@TK5EX14MBXC254.redmond.corp.microsoft.com>
The first sentence looks like a copy and paste issue from the Navigation Timing spec. It should be: "timing attributes are not skewed by adjustments to the system clock while fetching the resource." I will update the spec.

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.


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

I was reading through the Resource Timing spec again looking at the monotonic clock requirements. I had a couple of comments on it.

First, it says that "timing attributes are not skewed by adjustments to the system clock during the navigation." We might not be navigating when resources load, but they should still use a monotonic clock referenced from the initial page load so that we can construct an accurate timeline.

Also, what do we do about resources that load from iframes? Are they referenced from the iframe's navigation or from the root navigation? The latter seems most useful from my perspective, but maybe there are other concerns there.

Received on Monday, 15 August 2011 23:53:11 UTC

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