[Navigation Timing] domLoading missing
Reported by
nicjan...@gmail.com,
Aug 4 2017
|
|||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Steps to reproduce the problem:
1. performance.getEntriesByType("navigation")[0].domLoading
What is the expected behavior?
domLoading is a NavigationTiming1 and NavigationTiming2 timestamp:
https://www.w3.org/TR/navigation-timing-2/
Getting the PerformanceNavigationTiming object from the PerformanceTimeline (getEntriesByType("navigation")) should have a domLoading property.
Getting the property the "old" way from performance.timing works: performance.timing.domLoading
What went wrong?
performance.getEntriesByType("navigation")[0].domLoading === undefined
Did this work before? No
Does this work in other browsers? Yes
Chrome version: 59.0.3071.115 Channel: stable
OS Version: 10.0
Flash Version:
,
Aug 4 2017
Test case showing performance.timing.domLoading works: https://output.jsbin.com/coposik/quiet
,
Aug 4 2017
domLoading is not in NT2: https://www.w3.org/TR/navigation-timing-2/#sec-PerformanceNavigationTiming (and also undefined in chrome 61) Nic - feel free to reopen if I missed something.
,
Aug 5 2017
Yup, I forgot domLoading was removed from the NT2 interface, and only available in the "legacy" NT performance.timing: https://www.w3.org/TR/navigation-timing-2/#the-performancetiming-interface |
|||
►
Sign in to add a comment |
|||
Comment 1 by nicjan...@gmail.com
, Aug 4 2017