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

I think PR #234 captures the gist of this issue, and specifically advocates for use of background sync to avoid rolling our own, duplicated logic. Issue #240 tracks the necessary changes to the background sync specification. By including `newSubscription` in the event, we've also defined that the user agent is responsible for actually updating the subscription with the push service.

-- 
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-280747572