RE: [NavigationTiming] What's new and implemented in Nav Timing 2?

Nic, what would motivate you to use the new interface from libraries?
Which of the unimplemented members is there the most demand for from your users?

Boris has previously stated that the reason why Mozilla does not yet implement the new interface is due to the following issue. I’d be interested in his take on the rest of the spec.
https://github.com/w3c/navigation-timing/issues/1


-Todd

From: Nic Jansma [mailto:nic@nicj.net]
Sent: Wednesday, June 10, 2015 5:21 AM
To: Philippe Le Hegaret; public-web-perf@w3.org
Subject: Re: [NavigationTiming] What's new and implemented in Nav Timing 2?

IE does return an object for window.performance.getEntriesByType("navigation")

[cid:image001.png@01D0A47B.881B7D60]

Small edit, the spec does make one reference to window.performance.timing in Step 20.f of the Processing Model, which should probably be updated.


- Nic

http://nicj.net/


@NicJ
On 6/9/2015 3:49 PM, Philippe Le Hegaret wrote:
Navigation Timing 2 contains the following new features:
[[

  *   the definition of Performance interface was moved to [[PERFORMANCE-TIMELINE]];
  *   support for [[PERFORMANCE-TIMELINE]];
  *   support for [[HR-TIME]];
  *   timing information for link negotiation<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-linkNegotiationStart>;
  *   the number of redirects<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-redirectCount> since the last non-redirect navigation;
  *   protocol<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-linkNegotiationStart> information;
  *   transfer<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-transferSize>, encoded body<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-encodedBodySize> and decoded body<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-decodedBodySize> size information;
  *   support for prerender<http://microformats.org/wiki/rel-prerender> navigation [[prerender]].
  *   the domLoading<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-domLoading> attribute is deprecated.
  *   the secureConnectionStart<http://w3c.github.io/navigation-timing/#widl-PerformanceNavigationTiming-secureConnectionStart> attribute is now mandatory.
]]
http://www.w3.org/TR/navigation-timing-2/


The most basic addition has been:
 window.performance.getEntriesByType("navigation")

Yet, looking at implementations around, they all return an empty array, instead of an array of size one.

Do we know why we have a slow uptake for the refactored interface?

Philippe