[wpt-sync] Sync PR 46060 - Correct responseStart and similar timestamp for prefetches which blocked on head
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox128 fixed)
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 46060 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/46060
Details from upstream follow.
Jeremy Roman <jbroman@chromium.org> wrote:
Correct responseStart and similar timestamp for prefetches which blocked on head
In early revisions, prefetches could not be served until the response
head had arrived, and any navigation before that time would not wait for
the prefetch but issue a new request. Consequently, it sufficed to allow
these values to duplicate the previous timestamp, since these always
logically occur before navigation.Since Chromium's PerformanceResourceTiming and
PerformanceNavigationTiming implementations do this automatically in the
absence of valid timestamps, this was accomplished by preventing load
timing information from being included with a prefetched response.Instead, we should pass along the essential timestamps for computing
typical metrics, but simply adjust those that occur before fetchStart to
occur at the same time as it, as though they had completed
instantaneously (since, from the perspective of the user experience,
it's as though they had).See this doc for more info:
https://docs.google.com/document/d/1oESLkgpXysbl_FQMZ5Ahj3xtHW6d_UTcB-StJrS7a1U/editBug: 337199386,1382255
Change-Id: I8cdde8465f87c4893780c835222bfd303b05dfc1
Reviewed-on: https://chromium-review.googlesource.com/5502156
WPT-Export-Revision: 983bd3aea09e688a63cd09723e10759cf89cb8b2
|
Assignee | |
Comment 1•11 days ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=3dfcb1ac701e966780642c9454e9ea1e2695f9b9
|
|
Assignee | |
Comment 2•11 days ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Chrome, and Safari on GitHub CI
Total 4 tests and 1 subtests
Status Summary
Chrome
OK : 3
PASS : 2
FAIL : 1
TIMEOUT: 2
Safari
ERROR : 4
Links
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d63a1fb25050 [wpt PR 46060] - Correct responseStart and similar timestamp for prefetches which blocked on head, a=testonly https://hg.mozilla.org/integration/autoland/rev/8e109158d7e9 [wpt PR 46060] - Update wpt metadata, a=testonly
|
||
Comment 4•3 days ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/d63a1fb25050
https://hg.mozilla.org/mozilla-central/rev/8e109158d7e9
Description
•