Intent to Experiment: fetchLater API

[Ming-Ying Chung]

Contact emails

my...@chromium.org, deno...@chromium.org, pending-beac...@google.com

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

Search tags

beacon, pending beacon, page unload beacon, unload beacon, 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?

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.

[Yoav Weiss]

What milestones do you want to run the experiment in?

On Wed, Nov 15, 2023 at 8:10 AM Jesugbamigbe Daniel Fadipe <jdanie...@gmail.com> wrote:

Many thanks,

J Daniel Fadipe
07412666868

--
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 blink-dev+...@chromium.org.
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.

[Yoav Weiss]

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 <jdanie...@gmail.com> wrote:

Many thanks,

J Daniel Fadipe
07412666868

On Wed, 15 Nov 2023 at 08:09, Ming-Ying Chung <my...@chromium.org> wrote:

Contact emails

my...@chromium.org, denomoto@chromium.org, pending-beacon-exper...@google.com

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[Daisuke Enomoto]

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?

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 <yoav...@chromium.org> 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 <jdanie...@gmail.com> wrote:

Many thanks,

J Daniel Fadipe
07412666868

On Wed, 15 Nov 2023 at 08:09, Ming-Ying Chung <my...@chromium.org> wrote:

Contact emails

my...@chromium.org, deno...@chromium.org, pending-beac...@google.com

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[Yoav Weiss]

On Tue, Nov 21, 2023 at 9:54 AM Daisuke Enomoto <deno...@chromium.org> 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. 

[Ming-Ying Chung]

On Tue, Nov 21, 2023 at 6:29 PM Yoav Weiss <yoav...@chromium.org> wrote:

On Tue, Nov 21, 2023 at 9:54 AM Daisuke Enomoto <deno...@chromium.org> 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.

[Mike Taylor]

What milestones are you proposing for the Origin Trial?

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.

[Ming-Ying Chung]

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 <mike...@chromium.org> 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.

[Yoav Weiss]

LGTM to experiment M121-M126

[Ming-Ying Chung]

Hi API owners,

We are working on adding a new permissions policy "deferred-fetch" for this fetchLater API (overview, github discussion, chromium discussion, spec PR). 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

[Domenic Denicola]

Updates during an Origin Trial do not require re-approval. You might want to be careful about how it impacts existing users of the trial, but that's up to your team to decide.

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.