Re: [w3c/push-api] Firing `pushsubscriptionchange` when permission is regranted (#236)

collimarco left a comment (w3c/push-api#236)

@saschanaz Why the spec needs to be updated? We have been using the pushsubscriptionchange event for years (here you can see the code: https://pushpad.xyz/blog/web-push-error-410-the-push-subscription-has-expired-or-the-user-has-unsubscribed). Please don't make unnecessary breaking changes. The current pushsubscriptionchange event already supports the possibility to have only the new subscription (in case the old one is no longer available).

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

Message ID: <w3c/push-api/issues/236/2802753873@github.com>