Re: [w3ctag/design-reviews] Background fetch (#279)

> The optional `downloadTotal` dictionary member misled me by it's name. I think having it called something like `doNotExceed` 

`doNotExceed` kinda loses context. Eg, does it include upload bandwidth?

> (and then leave the UI stuff to the UA to figure out (which it should know by the server responses, etc.)

If you're downloading a DASH-style movie it could be 1000s of resources. It's going to take a long time for the browser to know much about the size.

> The registration.backgoundFetch object is similar to a map in many respects.

The main difference is it's async. I'd like to make it an async iterator at some point.

> In the spirit of not needing to re-activate the browser code to do UI updates,

The browser needs reactivated anyway so the responses can be handled/read/moved. I kinda like the idea of specifying this stuff ahead of time, but it feels like it loses functionality for not much gain.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/279#issuecomment-434785092