[wpt-sync] Sync PR 30280 - [navigation-timing] test PerformanceNavigationTiming's duration and responseEnd properties before, during, and after the load event
Categories
(Core :: Performance: General, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 30280 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/30280
Details from upstream follow.
b'Alex Christensen <achristensen@apple.com>' wrote:
[navigation-timing] test PerformanceNavigationTiming's duration and responseEnd properties before, during, and after the load event
This comes from https://bugs.webkit.org/show_bug.cgi?id=229751
Chrome and now WebKit agree that responseEnd and duration should be 0 before the load event
and they should be filled in as the information becomes available.
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 1•4 years ago
|
||
| Assignee | ||
Comment 2•4 years ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 1 subtests
Status Summary
Firefox
OK : 1
FAIL : 1
Chrome
OK : 1
PASS : 1
Safari
TIMEOUT: 2
Links
Details
New Tests That Don't Pass
/navigation-timing/nav2_test_response_end_and_duration_before_during_and_after_load_event.html
Check that performance.getEntriesByType('navigation')[0].responseEnd has reasonable values before and after the load has finished: FAIL (Chrome: PASS, Safari: TIMEOUT)
Comment 4•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/46ec6e191353
https://hg.mozilla.org/mozilla-central/rev/1aefa5bbde46
Description
•