What milestones do you want to run the experiment in?

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

>
> Many thanks,
>
> J Daniel Fadipe
> 07412666868
>
>
> On Wed, 15 Nov 2023 at 08:09, Ming-Ying Chung <m...@chromium.org> wrote:
>
>> Contact emailsm...@chromium.org, denom...@chromium.org,
>> pending-beacon-experim...@google.com
>>
>> Explainer
>> https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md
>>
>> Specificationhttps://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 componentBlink>Network>FetchAPI
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ENetwork%3EFetchAPI>
>>
>> Search tagsbeacon <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 reviewhttps://github.com/w3ctag/design-reviews/issues/887
>>
>> TAG review statusIssues 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 experimentationCollecting 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://flagsFetchLaterAPI
>>
>> Finch feature nameFetchLaterAPI
>>
>> Requires code in //chrome?True
>>
>> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1465781
>>
>> Launch bughttps://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 discussionsIntent 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 blink-dev+unsubscr...@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
>> <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 blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVvTRsLXPQkJEKOk8vusN%2B9F7mT0cptfvHjxQH%2BMjgGFA%40mail.gmail.com.

Reply via email to