[wpt-sync] Sync PR 62428 - [compression-dictionary] Add a test for same-origin no-cors fetch
Categories
(Core :: DOM: Networking, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox158 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 62428 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/62428
Details from upstream follow.
Frédéric Wang Nélar <fwang@igalia.com> wrote:
[compression-dictionary] Add a test for same-origin no-cors fetch
As of 2026/09/03, the PR against the fetch spec [1] says that
"HTTP-network compression-dictionary fetch" should fallback to
"HTTP-network fetch" if request's mode is "no-cors". However,
this seems to be a mistake since Chromium allows using compression
dictionaries for same-origin [2]. Chromium's behavior is already
implicitly covered by compressed-large-resources-001.tentative, which
checks "no-cors" fetches via img/script/link tags but this CL adds a
more straightforward test that is easier to compare against its
cross-origin version. The CL also adds dictionary ids to make the
test a bit more robust.[1] https://github.com/whatwg/fetch/pull/1854
[2] https://source.chromium.org/chromium/chromium/src/+/main:services/network/cors/cors_url_loader.cc;l=366?q=LOAD_CAN_USE_SHARED_DICTIONARY&ss=chromium%2Fchromium%2FsrcBug: 40255884
Change-Id: I879382048ed18d45b629a1b8ae2b5d0461d06cb3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8353624
Reviewed-by: Patrick Meenan \<pmeenan@chromium.org>
Commit-Queue: Frédéric Wang Nélar \<fwang@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1691778}
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 1•2 months ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=d9c75f5b1921fe8e7e5afb877bf1ab81bbe2b395
| Assignee | ||
Comment 2•2 months ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 31 tests and 2 subtests
Status Summary
Firefox
OK : 1[GitHub] 31[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt, Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt]
PASS: 2[GitHub] 92[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt, Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt]
FAIL: 1[GitHub] 12[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt, Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt]
Chrome
OK : 1
PASS: 3
Safari
OK : 1
PASS: 1
FAIL: 2
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /fetch/compression-dictionary/dictionary-decompression.tentative.https.html [wpt.fyi]
- Decompression using Brotli fails when dictionary hash mismatches:
FAIL - Decompression using Zstandard fails when dictionary hash mismatches:
FAIL
- Decompression using Brotli fails when dictionary hash mismatches:
- /fetch/compression-dictionary/dictionary-fetch-no-cors.tentative.https.html [wpt.fyi]
- Opaque responses resulting from cross-origin redirects in no-cors mode do not register dictionary:
FAIL(Chrome:PASS, Safari:FAIL)
- Opaque responses resulting from cross-origin redirects in no-cors mode do not register dictionary:
- /fetch/compression-dictionary/dictionary-fetch-timing-001.tentative.https.html [wpt.fyi]
- Timing of compression dictionary fetches for <link> element and Link header.:
FAIL
- Timing of compression dictionary fetches for <link> element and Link header.:
- /fetch/compression-dictionary/dictionary-fetch-timing-002.tentative.https.html [wpt.fyi]
- <link rel=compression-dictionary> are fetched after DOM operations.:
FAIL
- <link rel=compression-dictionary> are fetched after DOM operations.:
- /fetch/compression-dictionary/dictionary-fetch-with-link-connect-src-nonce.tentative.https.html [wpt.fyi]
- All <link rel=compression-dictionary> are blocked via CSP rule connect-src 'nonce-abc', even when they have a matching cryptographic nonce.:
FAIL
- All <link rel=compression-dictionary> are blocked via CSP rule connect-src 'nonce-abc', even when they have a matching cryptographic nonce.:
- /fetch/compression-dictionary/dictionary-fetch-with-link-connect-src.tentative.https.html [wpt.fyi]
- link rel=compression-dictionary can be blocked via connect-src.:
FAIL
- link rel=compression-dictionary can be blocked via connect-src.:
- /fetch/compression-dictionary/dictionary-match.tentative.https.html [wpt.fyi]
- Dictionary with unknown match-dest is not used for fetch() API:
FAIL - match-dest presence takes priority over longer match patterns:
FAIL
- Dictionary with unknown match-dest is not used for fetch() API:
- /fetch/compression-dictionary/dictionary-registration.tentative.https.html [wpt.fyi]
- Dictionary with 1025 character dictionary ID is not registered:
FAIL - Dictionary registration with dictionary ID (valid characters and backslash escaping):
FAIL
- Dictionary with 1025 character dictionary ID is not registered:
- /fetch/compression-dictionary/fetch-destination.tentative.https.html [wpt.fyi]
- HTMLLinkElement with rel=compression-dictionary fetches with a "compression-dictionary" string Request.destination:
FAIL
- HTMLLinkElement with rel=compression-dictionary fetches with a "compression-dictionary" string Request.destination:
Comment 4•2 months ago
|
||
| bugherder | ||
Description
•