Re: [w3c/push-api] Describe process for subscription updates (#132)

Excuse the late response... @martinthomson commented that the background Sync API is an answer to the robustness issue. However, [https://github.com/WICG/BackgroundSync/issues/114](https://github.com/WICG/BackgroundSync/issues/114) indicates that a service worker may not register for sync if it has no open clients (and if I'm understanding [https://wicg.github.io/BackgroundSync/spec/#syncmanager](https://wicg.github.io/BackgroundSync/spec/#syncmanager) correctly, it's in the spec). In which case, retry of a failed `pushSubscriptionChange` via sync isn't possible, unless the UA guarantees only to deliver `pushSubscriptionChange` events to a service worker when there is a client page open for it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/132#issuecomment-257373208