Re: [spec-reviews] Web Background Sync API (#95)

Discussed at the Melbourne F2F.

Overall, we're in favour of what you're doing here.

The document doesn't enumerate its error conditions; it would be nice if this was spelled out, or at least shown more in example code.

E.g., consider the situation when a service worker is woken up to do background sync, and inside that you register for another background sync; what are the implications -- should a UA allow that? How should they notify the user? Are there normative limitations, and if not, are there heuristics?

It would be great if there was an "explainer" document to show how to use background sync, and discussing some of the design decisions.

Allowing a browser to do things after a page is closed open a number of new issues, because users' mental models for the Web doesn't include this. For example, privacy (as discussed), power usage, bandwidth usage, etc. It would be really helpful if there were a separate document exploring these concerns and talking about potential mitigations; this would help not only users and implementers of background sync and future extensions to it, but also other features that have similar concerns (e.g., beacon, web push). The spec could then link to this document to help implementers.

Would you consider writing such a document?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/95#issuecomment-171807986