RE: navigationStart in NavigationTiming

In IE10, grabbing performance.timing from the console on an about:blank page gives me the following values:

unloadEventEnd		0
unloadEventStart	0
navigationStart	1368030410528
redirectEnd	0	
redirectStart	0
fetchStart	1368030410528
domainLookupStart	1368030410528
domainLookupEnd	1368030410528
connectStart	1368030410528
connectEnd	1368030410528
requestStart	1368030410528
responseStart	1368030410528
responseEnd	1368030410528
domLoading	1368030410528
domInteractive	1368030410537
domContentLoadedEventStart	1368030410539
domContentLoadedEventEnd	1368030410539
domComplete	1368030410539
loadEventEnd	1368030410541
loadEventStart	1368030410541

Here unloadEventStart/End are zero'd out, as there is no previous navigation, and redirectStart/End are zero'd out as there are no same origin redirects. All fetchStart, DNS, connect, request, and response values are equal to navigationStart, meaning zero deltas from navigationStart. The DOM processing attributes have updated timing values. If we are to define the expected about:blank behavior, the above approach seems to work.

However, it does look like Chrome and Firefox also define values here, but the values don't seem to match each other. Seeing that these timing values aren't very useful to site developers, we can just specify that user agents MUST define the attributes, to avoid throwing an exception, but add a SHOULD clause on the expected values. 

-----Original Message-----
From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] 
Sent: Wednesday, May 1, 2013 6:36 PM
To: Arvind Jain
Cc: Jatinder Mann;
Subject: Re: navigationStart in NavigationTiming

On 5/1/13 9:12 PM, Arvind Jain wrote:
> I mean to say the behavior is unspecified for "about:blank"

I frankly see no reason to leave this unspecified.  Worst-case, just define it to all 0 for initial about:blank.


Received on Wednesday, 8 May 2013 16:54:21 UTC