Contact emails
jakear...@chromium.org, pe...@chromium.org, raya...@chromium.org, na...@chromium.org
Spec
https://wicg.github.io/background-fetch/
Test Website
https://backgroundfetch.com/ (code here)
Summary
Background Fetch API provides a service worker based download and upload mechanism which is persistent across service worker and browser restarts.
The system provides a developer-controllable interface to schedule, query, pause, and cancel background downloads and uploads. After a scheduled fetch completes, the system will notify the developer of the outcome of the operation by sending an event to the service worker.
In progress downloads and uploads are handled by the download manager and will be visible to users in a notification. The user will be able to pause and cancel actions from that interface.
Downloads and uploads should continue even if the developer's website is not loaded in a tab, and if Chrome is closed, the download should resume when Chrome opens again.
Limitations
The current implementation has a few limitations, where it doesn’t completely align with the spec:
Only downloads are supported at this time.
Requests that require CORS preflight are blocked.
There’s no access to downloaded content while the download is in progress.
We’ll continue to iterate on the implementation, but the current state makes a number of use-cases work. It’s at a stage where we feel it’s important to start gathering feedback.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/Ia9_-CVrl1U/jEBQGVv_BQAJ
Goals for experimentation
To measure the real world impact of this feature before shipping. We will track the usage, error rates, stability and basic performance numbers. Experimentation will also let us gauge interest in the feature.
Experimental timeline
We’d like to run this for one or two milestones, starting with M71
(M71 cuts around Oct 11, will go Stable around beginning of Dec ~ end of Jan 2019)
Any risks when the experiment finishes?
Low.
Ongoing technical constraints
None.
Debuggability
Background Fetch initiated downloads are clearly identified at chrome://download-internals.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Yes, except WebView.
OWP launch tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=704729
Link to entry on the feature dashboard
https://www.chromestatus.com/features/5712608971718656
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3b74c99a-2d1c-4394-9a99-80879feafac5%40chromium.org.
Summary
Background Fetch API provides a service worker based download and upload mechanism which is persistent across service worker and browser restarts.
The system provides a developer-controllable interface to schedule, query, pause, and cancel background downloads and uploads. After a scheduled fetch completes, the system will notify the developer of the outcome of the operation by sending an event to the service worker.
In progress downloads and uploads are handled by the download manager and will be visible to users in a notification. The user will be able to pause and cancel actions from that interface.
--
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/925c9fdf-989e-4f87-96b9-4b0ffac03dc1%40chromium.org.