Re: navigationStart and the actual start of the navigation

Hello,

Having taken a look at Navigation Timing 2 and friends, it seems that it's
not that clear where (to which spec) a change of navigation start time
definition would belong to. Let me explain.

I understand that Navigation Timing 1 is pretty much in maintenance mode
and we would be making the change to Navigation Timing 2. However, as
Navigation Timing 2 is based on High Resolution Time, it does not define
(or even contain) the "navigationStart" attribute - instead, being
DOMHighResTimeStamps, its attributes are relative to the navigationStart of
the original NavigationTiming spec, as required by the High Resolution Time
spec.

So in order to have the change applied to Navigation Timing 2, we'd need to
either change the definition of DOMHighResTimeStamps in High Resolution
Time (severing the relation with navigationStart from Navigation Timing 1),
or actually make the change in Navigation Timing 1.

What do you guys think?

Cheers,
Przemek


On Wed, Jul 23, 2014 at 7:48 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 7/23/14, 1:07 PM, Przemysław Pietrzkiewicz wrote:
>
>> Agreed; I think that for some applications "most" will not be good
>> enough though.
>>
>
> My point was that typically the work beforeunload does will be perceived
> as part of the page load by the user.
>
>
>  Maybe recording navigationStart earlier but providing new
>> intermediate points so that it's possible to exclude the onbeforeunload
>> event if needed would be reasonable?
>>
>
> Sure.  Or, again, resetting the navigationStart time if a prompt is
> actually shown.
>
>  Wdyt?
>>
>
> Doesn't seem completely insane.
>
>
>  PS I'm ooo until the 4th of August with limited email access, apologies
>> for any inconvenience.
>>
>
> I'm likewise out Aug 5-19, fwiw.
>
> -Boris
>
>