- From: Marco Colli <notifications@github.com>
- Date: Wed, 25 May 2016 14:13:28 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc:
Received on Wednesday, 25 May 2016 21:13:56 UTC
+1 (obviously) I would like to remark that this issue should apply to the following cases: - the user blocks the notifications (a single pushsubscriptionchange is triggered passing the old subscription so that it can be immediately removed from the app server) - the push service invalidates the endpoint (a single pushsubscriptionchange is triggered passing the old subscription and a new endpoint can be obtained with `getSubscription()`, so that the old endpoint can be replaced with the new one on the server preserving attached data) --- 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/193#issuecomment-221709399
Received on Wednesday, 25 May 2016 21:13:56 UTC