fetchLater() is a JavaScript API to request a deferred fetch. Once called in a document, a deferred request is queued by the browser in the PENDING state, and will be invoked by the earliest of the following conditions: * The document is destroyed. * After a user-specified time. For privacy reason, all pending requests will be flushed upon document entering bfcache no matter how much time is left. * Browser decides it's time to send it. 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.
None
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
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
FetchLater is a new JS API.
There are no particular debugging APIs made available or Chrome DevTools integrations yet.
This is a JS API that will be available to Blink platforms.
https://wpt.fyi/results/fetch/fetch-later
Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?
N/AShipping on desktop | 134 |
Origin trial desktop first | 121 |
Origin trial desktop last | 126 |
Origin trial extension 1 end milestone | 132 |
DevTrial on desktop | 120 |
Shipping on Android | 134 |
Origin trial Android first | 121 |
Origin trial Android last | 126 |
DevTrial on Android | 120 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
https://github.com/whatwg/fetch/pull/1647--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67ac7ec8.2b0a0220.49add.2034.GAE%40google.com.
LGTM2
LGTM3
/Daniel
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0bf14b58-5428-444a-925c-58d09480a202%40chromium.org.