Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228)

Overall I'm +1 your proposal.

Assuming that the newSubscription would also be the result of calling `pushManager.subscribe(options)` then the approach I would expect most developers to take is to attempt subscribe the user, regardless of permission state or `event.newSubscription`, sending the result to their application server or catching the error. At the same time removing the old subscription from the backend by either using event.oldSubscription or their own indexeddb result.


-- 
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/228#issuecomment-263371384