Re: [NavigationTiming] Issues in the document.open test (or perhaps in the spec, if the test is correct)

• From: Carl-Anton Ingmarsson <carlantoni@opera.com>
• Date: Wed, 13 Jun 2012 12:37:31 +0200
• To: Boris Zbarsky <bzbarsky@MIT.EDU>
• Cc: public-web-perf@w3.org
• Message-ID: <1339583851.11202.8.camel@c-a-box>

> 
> So as far as I can tell, calling document.open and then document.close 
> should affect various navigation timing values (navigationStart, 
> domLoading, domComplete, loadEventStart, loadEventEnd, etc).  This is 
> what Gecko does.

It's also my understanding that document.open() document.close() should
affect all the non-network related attributes, e.g.

Should change: navigationStart, unloadEventStart, unloadEventEnd,
               domLoading, domInteractive,
               domContentLoadedEventStart, domContentLoadedEventEnd,
               domComplete, loadEventStart, loadEventEnd.

Should not change: redirectStart, redirectEnd, fetchStart,
                   domainLookupStart, domainLookupEnd,
                   connectStart, connectEnd,
                   secureConnectionStart, requestStart,
                   responseStart, responseEnd.

This of course means that navigationStart, unloadEventStart and
unloadEventEnd now can have values greater than the unchanged
attributes. Perhaps it's better to set all the unchanged attributes
(except redirect[Start|End]) to be the same as unloadEventEnd or
domLoading?

The tests expectation that all of the attributes should stay the same is
in my opinion completely wrong. I'd expect to be able to get timing data
of documents I create with document.open() document.close().

- Carl-Anton 

Received on Wednesday, 13 June 2012 12:08:26 UTC