[wpt-sync] Sync PR 46132 - Revert "[fetch-later] Define new permissions policy `deferred-fetch`"
Categories
(Core :: DOM: Networking, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 46132 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/46132
Details from upstream follow.
Anders Hartvoll Ruud <andruud@chromium.org> wrote:
Revert "[fetch-later] Define new permissions policy
deferred-fetch
"This reverts commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1.
Reason for revert: Suspected of causing crbug.com/339120680
Original change's description:
[fetch-later] Define new permissions policy
deferred-fetch
1-Pager: https://docs.google.com/document/d/1P70kdENIByy3qWabN5rUPmBVkkANNSOM_jZynLnqINY/edit
This CL follows the guide to define a new permissions policy
deferred-fetch
, which is used to gate the newfetchLater()
API.
Relevant WPT are added in this CL, and the subsequent CL will further
use this policy to adjust the request quota.In this CL,
deferred-fetch
is not added to chrome://settings/content
page. And no permission prompt for it.
- webappsec request: https://github.com/w3c/webappsec-permissions-policy/issues/544
- "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch
- "deferred-fetch" policy discussion: https://github.com/WICG/pending-beacon/issues/87#issuecomment-1985358609
- FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md
Bug: b:40276121
Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481
Reviewed-by: Adam Rice \<ricea@chromium.org>
Reviewed-by: Thomas Nguyen \<tungnh@chromium.org>
Reviewed-by: Ian Clelland \<iclelland@chromium.org>
Commit-Queue: Ming-Ying Chung \<mych@chromium.org>
Reviewed-by: Yoav Weiss (@Shopify) \<yoavweiss@chromium.org>
Reviewed-by: Takashi Toyoshima \<toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1297320}Bug: b:40276121, 339120680
Change-Id: I82b567642fb49429ad14cce676a4b8f4e1c673deReviewed-on: https://chromium-review.googlesource.com/5518461
WPT-Export-Revision: 23714a3fe960a857e66683ce3de1962bc6c6d2d3
Assignee | ||
Comment 1•9 months ago
|
||
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Comment 2•9 months ago
|
||
Assignee | ||
Comment 3•9 months ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 3 subtests
Status Summary
Firefox
FAIL
: 3
ERROR
: 1
Chrome
OK
: 1
PASS
: 3
Safari
FAIL
: 3
ERROR
: 1
Links
Details
New Tests That Don't Pass
- /fetch/fetch-later/iframe.tentative.https.window.html [wpt.fyi]:
ERROR
(Chrome:OK
, Safari:ERROR
)- A blank iframe can trigger fetchLater.:
FAIL
(Chrome:PASS
, Safari:FAIL
) - A same-origin iframe can trigger fetchLater.:
FAIL
(Chrome:PASS
, Safari:FAIL
) - A cross-origin iframe can trigger fetchLater.:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- A blank iframe can trigger fetchLater.:
Comment 5•8 months ago
|
||
bugherder |
Description
•