background-fetch
background-fetch copied to clipboard
WICG
API proposal for background downloading/uploading
The `backgroundfetched` and `backgroundfetchfail` events have init dictionaries that require a sequence of `BackgroundFetchSettledFetches` objects. (Note that it's not a sequence right now either.) However, `BackgroundFetchSettledFetches` is not constructable. It...
Feels like there should be a `BackgroundFetchSettledEvent` that the `fail` event uses, which `BackgroundFetchedEvent` extends to add `updateUI`
It doesn't really make sense to use foreign fetch with background fetch, it should be skipped.
The current proposal allows the browser to turn a single request into multiple range requests, allowing for pause/resume. However, what should we do if the request the user passes contains...
Given that @igrigorik and I are planning on merging `sendBeacon()` into `fetch()` and this offers similar functionality, but for the response scenario rather than the request scenario, it might be...
Worth looking at what browsers do right now with video range requests.
I wonder if we can reuse `fetch()` somehow. That way we don't have all the features of the Fetch API in two places. That already causes issues with the Cache...
While crawling [Background Fetch](https://wicg.github.io/background-fetch/), the following links to other specifications were detected as pointing to non-existing anchors, which should be fixed: * [ ] https://fetch.spec.whatwg.org/#concept-fetch-terminate * [ ] https://w3c.github.io/permissions/#permission-state *...
This way we can link to this eventually from https://github.com/w3c/permissions-registry *** Preview | Diff
imagine a senario that you need to download or upload large data. you don't want users to use up all mobile data. so the solution would be to only do...
