Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)

Indeed; the user can't unsubscribe if the browser is closed.

The case I'm talking about is when the push server drops the subscription, without a request from the browser. The server can do this for any reason, at any time: for example, if there are too many outstanding messages for that subscription, if the browser hasn't reconnected in a while, or if the server is running into storage limits.

In that case, the browser will fire a `pushsubscriptionchange` event the next time it reconnects to the push server. But, until then, sending messages to the dropped subscription will return a 404.

---
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/116#issuecomment-221668252