background-fetch
background-fetch copied to clipboard
WICG
API proposal for background downloading/uploading
This helps to clarify that it refers to the size of the data, not the size of the data down the wire (which could be encoded) or size on disk...
This should be done after #97, as it may be easier to link to the relevant info in the spec.
Just based on the names, I was confused on why we were building this when background sync already exists. From skimming https://developers.google.com/web/updates/2015/12/background-sync versus the intro to this document, it seems...
"Delete `Content-Length` from response’s header list." is duplicated under item 8 [here](https://wicg.github.io/background-fetch/#create-record-objects).
Use the ImageResource dictionary defined in the Web App Manifest spec (https://www.w3.org/TR/appmanifest/#imageresource-and-its-members) to pass the icons.
This might just be a case of moving the explainer examples into the spec.
I guess they should just put a conservative number down. Eg, allow 10k for each JSON response. We should add some UI guidance here too. If the upload sizes is...
If I add a request that has a stream for a body, but that stream never ends, it blocks additional bg fetches being registered until the stream provider is terminated....
In response to https://github.com/w3ctag/design-reviews/issues/279 Seeing examples like `event.updateUI(`Level ${level} ready to play!`);`, it is not clear to me as an app developer whether I would like that to be updated...
The constructor requires a BackgroundFetchSettledEventInit object, which in turn requires a BackgroundFetchSettledFetches object, which has no constructor.