Hi API owners, We are working on adding a new permissions policy "deferred-fetch" for this fetchLater API (overview <https://docs.google.com/document/d/1P70kdENIByy3qWabN5rUPmBVkkANNSOM_jZynLnqINY/edit> , github discussion <https://github.com/WICG/pending-beacon/issues/87#issuecomment-1985358609>, chromium discussion <https://chromium-review.googlesource.com/c/chromium/src/+/5367481/comment/44ce9e49_1fe2eef5/>, spec PR <https://github.com/whatwg/fetch/pull/1647>). While the API is still running in OT, we would like to know if we need to send an independent intent to make it include the new policy or not.
Thanks, Ming On Tue, Jan 16, 2024 at 2:35 PM Yoav Weiss <[email protected]> wrote: > LGTM to experiment M121-M126 > > On Tue, Jan 16, 2024 at 5:50 AM Ming-Ying Chung <[email protected]> wrote: > >> PTAL. Reviving this thread again. We still need Blink approval to proceed >> with OT. >> >> On Thu, Dec 14, 2023 at 6:16 AM Mike Taylor <[email protected]> >> wrote: >> >>> What milestones are you proposing for the Origin Trial? >>> >> Due to some internal review delay, we are now planning for OT from M121 >> to M126. The chromestatus entries have also been updated respectively. >> >> >> >>> On 12/13/23 1:48 AM, 'Ming-Ying Chung' via blink-dev wrote: >>> >>> On Tue, Nov 21, 2023 at 6:29 PM Yoav Weiss <[email protected]> >>> wrote: >>> >>>> >>>> >>>> On Tue, Nov 21, 2023 at 9:54 AM Daisuke Enomoto <[email protected]> >>>> wrote: >>>> >>>>> Yoav, >>>>> >>>>> What milestones do you want to run the experiment in? >>>>> >>>>> We plan to run the dev trial in 120. When we request an OT, would you >>>>> recommend us to send another I2E generated on chromestatus entry? >>>>> >>>> >>>> A dev trial doesn't require any approvals. Please revive this thread >>>> when you're ready to request an OT. >>>> >>> >>> Reviving this thread to request the OT approval. >>> >>> >>>> >>>>> Also, can you kick off the other review checks in your chromestatus >>>>>> entry? >>>>> >>>>> Yes, we have kicked off Security and Privacy reviews. >>>>> >>>>> >>>>> On Thu, Nov 16, 2023 at 12:42 AM Yoav Weiss <[email protected]> >>>>> wrote: >>>>> >>>>>> Also, can you kick off the other review checks in your chromestatus >>>>>> entry? >>>>>> >>>>>> On Wednesday, November 15, 2023 at 10:40:08 AM UTC+1 Yoav Weiss wrote: >>>>>> >>>>>>> What milestones do you want to run the experiment in? >>>>>>> >>>>>>> On Wed, Nov 15, 2023 at 8:10 AM Jesugbamigbe Daniel Fadipe < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> Many thanks, >>>>>>>> >>>>>>>> J Daniel Fadipe >>>>>>>> 07412666868 >>>>>>>> >>>>>>>> >>>>>>>> On Wed, 15 Nov 2023 at 08:09, Ming-Ying Chung <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>> Contact emails [email protected], [email protected], >>>>>>>>> [email protected] >>>>>>>>> >>>>>>>>> Explainer >>>>>>>>> https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md >>>>>>>>> >>>>>>>>> Specification https://whatpr.org/fetch/1647/9ca4bda...37a66c9.html >>>>>>>>> >>>>>>>>> Design docs >>>>>>>>> >>>>>>>>> https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md >>>>>>>>> >>>>>>>>> https://docs.google.com/document/d/1U8XSnICPY3j-fjzG35UVm6zjwL6LvX6ETU3T8WrzLyQ/edit#heading=h.ms1oipx914vf >>>>>>>>> >>>>>>>>> Summary >>>>>>>>> >>>>>>>>> fetchLater() is a JavaScript API to request a deferred fetch. Once >>>>>>>>> called, the request is queued by the browser, and will be invoked in >>>>>>>>> one of >>>>>>>>> the following scenarios: • The document is destroyed. • After a >>>>>>>>> certain >>>>>>>>> time. The API returns a FetchLaterResult that contains a boolean field >>>>>>>>> "activated" that may be updated to tell whether the deferred request >>>>>>>>> has >>>>>>>>> been sent out or not. On successful sending, the whole response will >>>>>>>>> be >>>>>>>>> ignored by browser, including body and headers. Nothing at all should >>>>>>>>> be >>>>>>>>> processed or updated, as the page may have already be gone. Note that >>>>>>>>> from >>>>>>>>> the point of view of the API user, the exact send time is unknown. >>>>>>>>> >>>>>>>>> >>>>>>>>> Blink component Blink>Network>FetchAPI >>>>>>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ENetwork%3EFetchAPI> >>>>>>>>> >>>>>>>>> Search tags beacon <https://chromestatus.com/features#tags:beacon> >>>>>>>>> , pending beacon >>>>>>>>> <https://chromestatus.com/features#tags:pending%20beacon>, page >>>>>>>>> unload beacon >>>>>>>>> <https://chromestatus.com/features#tags:page%20unload%20beacon>, >>>>>>>>> unload >>>>>>>>> beacon <https://chromestatus.com/features#tags:unload%20beacon>, >>>>>>>>> fetchlater <https://chromestatus.com/features#tags:fetchlater> >>>>>>>>> >>>>>>>>> TAG review https://github.com/w3ctag/design-reviews/issues/887 >>>>>>>>> >>>>>>>>> TAG review status Issues addressed >>>>>>>>> >>>>>>>>> Risks >>>>>>>>> >>>>>>>>> >>>>>>>>> Interoperability and Compatibility >>>>>>>>> >>>>>>>>> None >>>>>>>>> >>>>>>>>> >>>>>>>>> *Gecko*: Positive ( >>>>>>>>> https://github.com/mozilla/standards-positions/issues/703) >>>>>>>>> >>>>>>>>> *WebKit*: Positive ( >>>>>>>>> https://github.com/WebKit/standards-positions/issues/85) >>>>>>>>> >>>>>>>>> *Web developers*: Positive ( >>>>>>>>> https://discourse.wicg.io/t/proposal-stateful-javascript-page-unload-beacon-api/5776 >>>>>>>>> ) >>>>>>>>> >>>>>>>>> *Other signals*: W3C WebPerf: >>>>>>>>> https://w3c.github.io/web-performance/meetings/2022/2022-03-31/index.html >>>>>>>>> >>>>>>>>> Security >>>>>>>>> >>>>>>>>> >>>>>>>>> https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md#security-considerations >>>>>>>>> https://docs.google.com/document/d/1U8XSnICPY3j-fjzG35UVm6zjwL6LvX6ETU3T8WrzLyQ/edit?pli=1#heading=h.kztg1uvdyoki >>>>>>>>> >>>>>>>>> >>>>>>>>> WebView application risks >>>>>>>>> >>>>>>>>> Does this intent deprecate or change behavior of existing APIs, >>>>>>>>> such that it has potentially high risk for Android WebView-based >>>>>>>>> applications? >>>>>>>>> >>>>>>>>> None >>>>>>>>> >>>>>>>>> >>>>>>>>> Goals for experimentation Collecting feedbacks around the >>>>>>>>> stability of the fetchLater API, and whether to provide more useful >>>>>>>>> API or >>>>>>>>> to update its behavior model. >>>>>>>>> >>>>>>>>> Ongoing technical constraints >>>>>>>>> >>>>>>>>> See >>>>>>>>> https://chromium.googlesource.com/chromium/src/+/main/docs/experiments/fetch-later.md#what_s-not-supported >>>>>>>>> for what's supported and what's not supported in the OT >>>>>>>>> implementation. >>>>>>>>> >>>>>>>>> >>>>>>>>> Debuggability >>>>>>>>> >>>>>>>>> There are no particular debugging APIs made available or Chrome >>>>>>>>> DevTools integrations yet. >>>>>>>>> >>>>>>>>> >>>>>>>>> Will this feature be supported on all six Blink platforms >>>>>>>>> (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? >>>>>>>>> Yes >>>>>>>>> >>>>>>>>> This is a JS API that will be available to Blink platforms. >>>>>>>>> >>>>>>>>> >>>>>>>>> Is this feature fully tested by web-platform-tests >>>>>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>>>>>> ? Yes >>>>>>>>> >>>>>>>>> https://wpt.fyi/results/fetch/fetch-later >>>>>>>>> >>>>>>>>> >>>>>>>>> DevTrial instructions >>>>>>>>> https://chromium.googlesource.com/chromium/src/+/main/docs/experiments/fetch-later.md >>>>>>>>> >>>>>>>>> Flag name on chrome://flags FetchLaterAPI >>>>>>>>> >>>>>>>>> Finch feature name FetchLaterAPI >>>>>>>>> >>>>>>>>> Requires code in //chrome? True >>>>>>>>> >>>>>>>>> Tracking bug >>>>>>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1465781 >>>>>>>>> >>>>>>>>> Launch bug https://launch.corp.google.com/launch/4272588 >>>>>>>>> >>>>>>>>> Estimated milestones >>>>>>>>> DevTrial on desktop 120 >>>>>>>>> DevTrial on Android 120 >>>>>>>>> >>>>>>>>> Link to entry on the Chrome Platform Status >>>>>>>>> https://chromestatus.com/feature/4654499737632768 >>>>>>>>> >>>>>>>>> Links to previous Intent discussions Intent to prototype: >>>>>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/KXnqpUpVwPQ >>>>>>>>> >>>>>>>>> This intent message was generated by Chrome Platform Status >>>>>>>>> <https://chromestatus.com/>. >>>>>>>>> >>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "blink-dev" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to [email protected]. >>>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAH3JASUZRWPgtO7b%3DQ%2BXOEEg7LMXnuoq3PFVv_EpARwbntf-ZQ%40mail.gmail.com >>>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAH3JASUZRWPgtO7b%3DQ%2BXOEEg7LMXnuoq3PFVv_EpARwbntf-ZQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "blink-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B_JMTxqK4wCYjU0XpN_VijzB5TFmg2mnzkq1XfBqiivQjtAFQ%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B_JMTxqK4wCYjU0XpN_VijzB5TFmg2mnzkq1XfBqiivQjtAFQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B_JMTzXuFvipsj_C22MY%3DqyUE93uBLrufp1o3MNpdHmAACXhg%40mail.gmail.com.
