background-fetch

background-fetch copied to clipboard

Support retrying of uploads

2

It feels like something we shouldn't do by default, as making the same "`POST`" request twice may have side effects. Perhaps we should provide an opt-in to this? Something that...

jakearchibald

Status?

7

Hi folks, what's the status on this work? Enough interest for the Service Worker WG is willing to take it?

marcoscaceres

Don't require Cache API to have a secure context

4

It seems to only require a secure context due to being bundled with Service Workers, but Service Workers are not required for the cache API to be used or have...

aerik

Fix bikeshed errors in fetch callbacks

2

jakearchibald

Make bikeshed complain less

5

It seems there's a lot of busted links. I'll fix... some of them.

miketaylr

I was looking at https://github.com/whatwg/fetch/issues/771 and noticed that this specification doesn't define a guard for its `Headers` objects. Might also not be tested? (Probably best to fix this on top...

annevk

Once #153, #154, and #155 are tackled, do you agree on moving "validate a partial response", "extract content-range values", and "single byte content-range" into Fetch? It seems these will be...

annevk

Content-Range header parsing

2

I looked at https://wicg.github.io/background-fetch/#extract-content-range-values and one problem I found is that this will lead to different results between ``` Content-Range: x, y ``` and ``` Content-Range: x Content-Range: y ```...

annevk

ok status vs 200/206

1

It seems that for media elements we will require 200 or 206, whereas this specification seems to allow 206 or 2xx. Should that be tightened?

annevk

It seems that * in the algorithm is a byte, not a string, so it should use the backtick syntax, right?

annevk