Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better describe error conditions in spec #121

Open
jkarlin opened this issue Jan 15, 2016 · 0 comments
Open

Better describe error conditions in spec #121

jkarlin opened this issue Jan 15, 2016 · 0 comments

Comments

@jkarlin
Copy link
Collaborator

jkarlin commented Jan 15, 2016

As requested by TAG review (w3ctag/design-reviews#95), we need to better describe the error conditions.

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant