Permissions Policy `deferred-fetch` and `deferred-fetch-minimal` #544

mingyc · 2024-03-15T08:32:21Z

Update: The latest proposal (and implementation in Chromium) includes two new permissions policy deferred-fetch and deferred-fetch-minimal. But at the time of initial post it was only deferred-fetch.

The example usage and full explaination can be found at https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md#quota-and-permissions-policy

--

For the new deferred fetching (fetchLater) API (explainer, Spec PR), we would like to propose a new permissions policy deferred-fetch to help developers manage the quota for all fetchLater requests that can be fired within their documents.

The discussion happened in WICG/pending-beacon#87, and in the comment we proposed to add deferred-fetch along with its usage.

Specifically, the main motivation is that, without any constraints, every frame can queue an unlimited number of fetchLater requests, which may use up network resources. However, unlike other types of JS-initiated requests, there is no way for users to be able to terminate pending fetchLater requests, as closing a tab will simply trigger sending all fetchLater requests on it.

While setting a quota for individual sites, we would also like to prevent (1) leaking cross-site activity and (2) abusing by creating additional frames.

@noamr @annevk @yoavweiss @nicjansma

The text was updated successfully, but these errors were encountered:

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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md Bug: b:40276121 Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d

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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md Bug: b:40276121 Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 Reviewed-by: Adam Rice <[email protected]> Reviewed-by: Thomas Nguyen <[email protected]> Reviewed-by: Ian Clelland <[email protected]> Commit-Queue: Ming-Ying Chung <[email protected]> Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> Reviewed-by: Takashi Toyoshima <[email protected]> Cr-Commit-Position: refs/heads/main@{#1297320}

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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121, 339120680 Change-Id: I82b567642fb49429ad14cce676a4b8f4e1c673de

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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121, 339120680 Change-Id: I82b567642fb49429ad14cce676a4b8f4e1c673de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518461 Commit-Queue: Anders Hartvoll Ruud <[email protected]> Bot-Commit: Rubber Stamper <[email protected]> Owners-Override: Anders Hartvoll Ruud <[email protected]> Cr-Commit-Position: refs/heads/main@{#1297378}

This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936

This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121,339120680 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936

This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 The error message from https://crbug.com/339120680 is removed by https://crrev.com/c/5524593/1..2 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121,339120680 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121,339120680 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936

This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 The error message from https://crbug.com/339120680 is removed by https://crrev.com/c/5524593/1..2 as the same behavior is already covered by `/fetch/fetch-later/permissions-policy/deferred-fetch-default-permissions-policy.tentative.https.window.js` 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121,339120680 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121,339120680 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936

This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 The failed test from https://crbug.com/339120680 is removed by https://crrev.com/c/5524593/1..2 as the same behavior is already covered by `/fetch/fetch-later/permissions-policy/deferred-fetch-default-permissions-policy.tentative.https.window.js` more carefully. 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121,339120680 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121,339120680 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936

…icy `deferred-fetch`, a=testonly Automatic update from web-platform-tests [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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md Bug: b:40276121 Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 Reviewed-by: Adam Rice <[email protected]> Reviewed-by: Thomas Nguyen <[email protected]> Reviewed-by: Ian Clelland <[email protected]> Commit-Queue: Ming-Ying Chung <[email protected]> Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> Reviewed-by: Takashi Toyoshima <[email protected]> Cr-Commit-Position: refs/heads/main@{#1297320} -- wpt-commits: 8562ff94a7d5463f74d553a404f84bf240ae2386 wpt-pr: 45153

…ions policy `deferred-fetch`", a=testonly Automatic update from web-platform-tests 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121, 339120680 Change-Id: I82b567642fb49429ad14cce676a4b8f4e1c673de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518461 Commit-Queue: Anders Hartvoll Ruud <[email protected]> Bot-Commit: Rubber Stamper <[email protected]> Owners-Override: Anders Hartvoll Ruud <[email protected]> Cr-Commit-Position: refs/heads/main@{#1297378} -- wpt-commits: 1e6ef7ec83db226a120ae789090dd570a49a21fd wpt-pr: 46132

…icy `deferred-fetch`, a=testonly Automatic update from web-platform-tests [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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md Bug: b:40276121 Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 Reviewed-by: Adam Rice <[email protected]> Reviewed-by: Thomas Nguyen <[email protected]> Reviewed-by: Ian Clelland <[email protected]> Commit-Queue: Ming-Ying Chung <[email protected]> Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> Reviewed-by: Takashi Toyoshima <[email protected]> Cr-Commit-Position: refs/heads/main@{#1297320} -- wpt-commits: 8562ff94a7d5463f74d553a404f84bf240ae2386 wpt-pr: 45153

…ions policy `deferred-fetch`", a=testonly Automatic update from web-platform-tests 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121, 339120680 Change-Id: I82b567642fb49429ad14cce676a4b8f4e1c673de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518461 Commit-Queue: Anders Hartvoll Ruud <[email protected]> Bot-Commit: Rubber Stamper <[email protected]> Owners-Override: Anders Hartvoll Ruud <[email protected]> Cr-Commit-Position: refs/heads/main@{#1297378} -- wpt-commits: 1e6ef7ec83db226a120ae789090dd570a49a21fd wpt-pr: 46132

This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 The failed test from https://crbug.com/339120680 is removed by https://crrev.com/c/5524593/1..2 as the same behavior is already covered by `/fetch/fetch-later/permissions-policy/deferred-fetch-default-permissions-policy.tentative.https.window.js` more carefully. 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121,339120680 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121,339120680 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936

This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 The failed test from https://crbug.com/339120680 is removed by https://crrev.com/c/5524593/1..2 as the same behavior is already covered by `/fetch/fetch-later/permissions-policy/deferred-fetch-default-permissions-policy.tentative.https.window.js` more carefully. 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121,339120680 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121,339120680 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5524593 Reviewed-by: Thomas Nguyen <[email protected]> Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> Reviewed-by: Ian Clelland <[email protected]> Commit-Queue: Ming-Ying Chung <[email protected]> Reviewed-by: Takashi Toyoshima <[email protected]> Reviewed-by: Adam Rice <[email protected]> Cr-Commit-Position: refs/heads/main@{#1310429}

…ions policy `deferred-fetch`", a=testonly Automatic update from web-platform-tests Reland "[fetch-later] Define new permissions policy `deferred-fetch`" This is a reland of commit 193729386996ac0bd40dba0aa98b7f85ff7b94d1 The failed test from https://crbug.com/339120680 is removed by https://crrev.com/c/5524593/1..2 as the same behavior is already covered by `/fetch/fetch-later/permissions-policy/deferred-fetch-default-permissions-policy.tentative.https.window.js` more carefully. 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 new `fetchLater()` 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: w3c/webappsec-permissions-policy#544 > - "deferred-fetch" usage in fetchLater draft spec: https://whatpr.org/fetch/1647.html#request-a-deferred-fetch > - "deferred-fetch" policy discussion: WICG/pending-beacon#87 (comment) > - FetchLater Explainer: https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > > [guide]: https://chromium.googlesource.com/chromium/src/+/main/components/permissions/add_new_permission.md > > Bug: b:40276121,339120680 > Change-Id: I2db4dd7484610fefb50c463552155b220f13ac5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5367481 > Reviewed-by: Adam Rice <[email protected]> > Reviewed-by: Thomas Nguyen <[email protected]> > Reviewed-by: Ian Clelland <[email protected]> > Commit-Queue: Ming-Ying Chung <[email protected]> > Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> > Reviewed-by: Takashi Toyoshima <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1297320} Bug: b:40276121,339120680 Change-Id: I41e2f0980f5d72eb6c0687a82d96ad4a59f59936 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5524593 Reviewed-by: Thomas Nguyen <[email protected]> Reviewed-by: Yoav Weiss (@Shopify) <[email protected]> Reviewed-by: Ian Clelland <[email protected]> Commit-Queue: Ming-Ying Chung <[email protected]> Reviewed-by: Takashi Toyoshima <[email protected]> Reviewed-by: Adam Rice <[email protected]> Cr-Commit-Position: refs/heads/main@{#1310429} -- wpt-commits: cdd00c8bc0a087353a9dc26e80f11c87aa4fdfae wpt-pr: 46159

Closes: w3c#544

chromium-wpt-export-bot mentioned this issue Mar 18, 2024

[fetch-later] Define new permissions policy deferred-fetch web-platform-tests/wpt#45153

Merged

mingyc mentioned this issue Mar 25, 2024

Request Limit WICG/pending-beacon#87

Open

chromium-wpt-export-bot mentioned this issue May 7, 2024

Revert "[fetch-later] Define new permissions policy deferred-fetch" web-platform-tests/wpt#46132

Merged

chromium-wpt-export-bot mentioned this issue May 8, 2024

Reland "[fetch-later] Define new permissions policy deferred-fetch" web-platform-tests/wpt#46159

Merged

clelland added a commit to clelland/feature-policy that referenced this issue Sep 21, 2024

Add 'deferred-fetch' as proposed feature

dedd81f

Closes: w3c#544

clelland closed this as completed Sep 21, 2024

mingyc changed the title ~~Permissions Policy "deferred-fetch"~~ Permissions Policy deferred-fetch and deferred-fetch-minimal Apr 3, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Permissions Policy `deferred-fetch` and `deferred-fetch-minimal` #544

Permissions Policy `deferred-fetch` and `deferred-fetch-minimal` #544

mingyc commented Mar 15, 2024 •

edited

Loading

Permissions Policy deferred-fetch and deferred-fetch-minimal #544

Permissions Policy deferred-fetch and deferred-fetch-minimal #544

Comments

mingyc commented Mar 15, 2024 • edited Loading

Permissions Policy `deferred-fetch` and `deferred-fetch-minimal` #544

Permissions Policy `deferred-fetch` and `deferred-fetch-minimal` #544

mingyc commented Mar 15, 2024 •

edited

Loading