[wpt-sync] Sync PR 37464 - Moved the fetch parts of the priority hints tests
Categories
(Core :: DOM: Networking, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 37464 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/37464
Details from upstream follow.
Patrick Meenan <pmeenan@chromium.org> wrote:
Moved the fetch parts of the priority hints tests
Moved the fetch parts of the priority hints tests into fetch as we're
getting ready to land the spec changes.This also adds tests that successful use of the priority requestinit
attribute works as expected and that the internal-only attributes
(blocking, priority and internalpriority) are not exposed on Request.Bug: 1301942
Change-Id: I311fba04587d1eb50b89c0f9303ac628d86a9529
Reviewed-on: https://chromium-review.googlesource.com/4097472
WPT-Export-Revision: 6157897c3a24b3e7c2e3152ff2e3e253e55b1b0f
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Comment 2•2 years ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 6 tests and 24 subtests
Status Summary
Firefox
OK
: 6
PASS
: 96
FAIL
: 16
Chrome
OK
: 6
PASS
: 104
FAIL
: 8
Safari
OK
: 6
PASS
: 96
FAIL
: 16
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /fetch/api/request/request-init-priority.any.worker.html [wpt.fyi]
- new Request() throws a TypeError if any of RequestInit's members' values are invalid:
FAIL
(Chrome:PASS
, Safari:FAIL
) - fetch() with an invalid priority returns a rejected promise with a TypeError:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- new Request() throws a TypeError if any of RequestInit's members' values are invalid:
- /fetch/api/request/request-init-priority.any.html [wpt.fyi]
- new Request() throws a TypeError if any of RequestInit's members' values are invalid:
FAIL
(Chrome:PASS
, Safari:FAIL
) - fetch() with an invalid priority returns a rejected promise with a TypeError:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- new Request() throws a TypeError if any of RequestInit's members' values are invalid:
- /fetch/api/request/request-structure.any.html [wpt.fyi]
- Check isReloadNavigation attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
) - Check isHistoryNavigation attribute:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Check duplex attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
)
- Check isReloadNavigation attribute:
- /fetch/api/request/request-structure.any.sharedworker.html [wpt.fyi]
- Check isReloadNavigation attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
) - Check isHistoryNavigation attribute:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Check duplex attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
)
- Check isReloadNavigation attribute:
- /fetch/api/request/request-structure.any.serviceworker.html [wpt.fyi]
- Check isReloadNavigation attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
) - Check isHistoryNavigation attribute:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Check duplex attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
)
- Check isReloadNavigation attribute:
- /fetch/api/request/request-structure.any.worker.html [wpt.fyi]
- Check isReloadNavigation attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
) - Check isHistoryNavigation attribute:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Check duplex attribute:
FAIL
(Chrome:FAIL
, Safari:FAIL
)
- Check isReloadNavigation attribute:
Assignee | ||
Updated•2 years ago
|
Comment 5•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1b35096d94f4
https://hg.mozilla.org/mozilla-central/rev/96c1b50e1e10
Description
•