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

Re: [ResourceTiming] startTime definition

From: James Simonsen <simonjam@chromium.org>
Date: Thu, 17 May 2012 18:05:56 -0700
Message-ID: <CAPVJQi=7fba0ovXosXaGExGBXdW-cGqcCEk2_xVmTitkKDM4aA@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Thu, May 17, 2012 at 3:59 PM, Jatinder Mann <jmann@microsoft.com> wrote:

>  “The startTime attribute must return a DOMHighResTimeStamp<http://www.w3.org/TR/hr-time/#domhighrestimestamp>with the time immediately before the user agent starts to queue the
> resource for fetching<http://www.w3.org/TR/html5/fetching-resources.html#fetch>.
> If there are HTTP redirects or equivalent<http://www.w3.org/TR/html5/fetching-resources.html#concept-http-equivalent-codes>when fetching the resource, this attribute must return a
> DOMHighResTimeStamp <http://www.w3.org/TR/hr-time/#domhighrestimestamp>with the time immediately before the user agent starts to queue the
> fetch <http://www.w3.org/TR/html5/fetching-resources.html#fetch> that
> initiates the redirect process for the resource.”
>

Can we just drop the second sentence? The fetching algorithm already talks
about redirects, so I don't think we need to call them out separately here.

James
Received on Friday, 18 May 2012 01:06:27 UTC

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