RE: [NavigationTiming] Updates

The addition of requestCount and uniqueDomains is intended to describe at the top-level if the root document was request intensive and from multiple domains.  This type of information can complement Resource Timing as those details are soon to be flushed out.

Our recommendation is to bake this into the NavigationInfo interface while we are working on the draft for Resource Timing.

An alternative option is that we can re-visit these attributes while we are flushing out the design and details for the Resource Timing interface.


Anderson Quach
IE Program Manager

From: [] On Behalf Of Anderson Quach
Sent: Monday, August 30, 2010 5:52 PM
To: Zhiheng Wang;
Subject: RE: [NavigationTiming] Updates

Thanks for the updates to the Navigation Timing working draft [1].

There are a couple of attributes that would add value to describing the navigation. We would like to get your feedback on the requestCount and uniqueDomains that was introduced in IE9's PPB3 [2].

Specifically, a count of the number of requests made by the root document and from the number of unique domains. These attributes can be provided under the window.performance.navigation object.

window.msPerformance.navigation.requestCount  -- the number of requests as specified by the root document.

window.msPerformance.navigation.uniqueDomains - the number of unique domain name requests made by the root document.

Best Regards,


From: [] On Behalf Of Zhiheng Wang
Sent: Friday, August 27, 2010 3:52 PM
To: public-web-perf
Subject: [NavigationTiming] Updates

    Based on the last conversation, the NavigationTiming has just been updated with the following changes:

   * DOM-related timing, i.e., domLoading, domInteractive, domContentLoad and domComplete, are added.
   * navigationStart now happens immediate after the user agent prompts for unloading the document.


Received on Thursday, 16 September 2010 01:01:52 UTC