Closed Bug 765933 Opened 12 years ago Closed 10 years ago

Implement the Performance Timeline spec

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla31

People

(Reporter: jaws, Unassigned)

References

(
URL
)

Details

(Whiteboard: [fixed by bug 822480])

See the (currently Editor's Draft) at the associated URL. Implementing this will help web authors as well as our native devtools timeline feature.
I've updated the URL with a link to the Working Draft.
URL: http://w3c-test.org/webperf/specs/Per... → http://www.w3.org/TR/performance-time...
Depends on: 782751
Blocks: 782751
No longer depends on: 782751
This spec actual has Recommendation state: http://www.w3.org/TR/2013/REC-performance-timeline-20131212/ Chrome and IE11 support it now, but Firefox still not. Looks like IE11 implement sth from Navigation Timing 2 too, when we use getEntries*() method: http://www.w3.org/TR/2014/WD-navigation-timing-2-20140325/ http://www.w3.org/wiki/Web_Performance/EntryType
Latest actual URL is http://www.w3.org/TR/user-timing/
No longer blocks: 782751
URL: http://dvcs.w3.org/hg/webperf/raw-fil... → http://www.w3.org/TR/user-timing/
Summary: Implement the Performance Timeline spec → Implement the User Timing spec
URL: http://www.w3.org/TR/user-timing/ → http://www.w3.org/TR/performance-time...
Summary: Implement the User Timing spec → Implement the Performance Timeline spec
Blocks: 782751
Looks like this was implemented during the implementation of the Resource Timing API, bug 822480.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 822480]
Target Milestone: --- → mozilla31
It's not implemented. http://www.w3.org/TR/performance-timeline/ typeof performance.getEntries === undefined
Alexey it has been already implemented in Firefox (together with Resource Timing API): https://developer.mozilla.org/en-US/Firefox/Releases/31 but before Firefox 35 (maybe) it was hide by dom.enable_resource_timing pref.
I see all the performance timeline methods in Nightly 36.0a1: https://cloudup.com/c-4TNTnSraK
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.