- From: Todd Reifsteck <toddreif@microsoft.com>
- Date: Tue, 17 Mar 2015 04:07:15 +0000
- To: Boris Zbarsky <bzbarsky@mit.edu>, "public-web-perf@w3.org" <public-web-perf@w3.org>
- CC: Tobin Titus <tobint@microsoft.com>
Thanks for the info, Boris. Glad to see user marks lighting up in Firefox!
I observe that we have an issue open on Navigation Timing 2 but haven't resolved it in any way:
https://github.com/w3c/navigation-timing/issues/1
I've added comments there so we can drive closure on this spec issue.
-----Original Message-----
From: Boris Zbarsky [mailto:bzbarsky@mit.edu]
Sent: Monday, March 16, 2015 7:27 PM
To: public-web-perf@w3.org
Subject: Re: ACTION-153: Check getentrybytype("navigation-timing") usage
On 3/16/15 9:49 PM, Todd Reifsteck wrote:
> performance.getEntriesByName('document') returns navigation timing. //
> IMPLEMENTED BY IE. MISSING IN CHROME/FIREFOX
See thread starting
<https://lists.w3.org/Archives/Public/public-web-perf/2014Jun/0015.html>
from 9 months ago or so. Has something actually changed in the spec drafts since then to make them make sense around this stuff?
> performance.getEntriesByName(<name>) returns all user timings with the
> name, <name>. // IMPLEMENTED BY CHROME/IE. Performance.mark MISSING IN
> FIREFOX
User timing is implemented in Firefox 38, for what it's worth.
> performance.getEntriesByType('navigation') returns navigation timing.
> // IMPLEMENTED BY IE. MISSING IN CHROME/FIREFOX
This is the same issue as the "document" one above.
-Boris
Received on Tuesday, 17 March 2015 04:07:52 UTC