W3C home > Mailing lists > Public > public-web-perf@w3.org > June 2014

Re: navigationStart and the actual start of the navigation

From: Arvind Jain <arvind@google.com>
Date: Fri, 27 Jun 2014 07:05:21 -0700
Message-ID: <CAOYaDdN1jT5MchiN6otK3y8NHui24SyYr=OUSaRTsCo5y73kHA@mail.gmail.com>
To: Przemysław Pietrzkiewicz <ppi@google.com>
Cc: public-web-perf <public-web-perf@w3.org>, Tony Gentilcore <tonyg@google.com>, Camille Lamy <clamy@google.com>, Ilya Grigorik <igrigorik@google.com>
It makes sense to me. I can make the change. Does anyone else have
comments on this?

On Fri, Jun 27, 2014 at 6:39 AM, Przemysław Pietrzkiewicz
<ppi@google.com> wrote:
> Hello,
>
> navigationStart for navigations without the previous document is described
> in [1] as follows:
>
> "If there is no previous document, this attribute must return the time the
> current document is created."
>
> What does "time the current document is created" mean? If read in terms of
> terminology we use in Chromium/Blink, that would be the time when we start
> loading the page in the renderer.
>
> But this can happen long time after the "open link in new tab" button is
> clicked. For instance, on Android spawning a new renderer takes significant
> time. Under current definition, the time needed to spawn the renderer would
> not be represented in the reported values.
>
> Would it make sense to define "navigationStart" as follows:
>
> "This attribute must return the time when the user agent determines that the
> navigation will happen. For navigations from existing documents, this is the
> time when the user agent finishes prompting to unload the previous
> document."
>
> ?
>
> Relevant discussion in the Chromium bug tracker: http://crbug.com/376004 .
>
> Wdyt?
>
> Cheers,
> Przemek
>
> [1]
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
Received on Friday, 27 June 2014 14:05:49 UTC

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