Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400)

saschanaz left a comment (w3c/push-api#400)

So I briefly revisited our implementation and filed https://bugzilla.mozilla.org/show_bug.cgi?id=1961806, with the following comment:

> But the point of having pushsubscriptionchange event is to notify the app servers so that they can learn the given endpoint is now revoked and should not be pinged. It would probably make sense not to fire the event immediately after permission change, but would also be too late to fire it only on regrant.

If the permission is revoked by clearing site data, it would probably make sense to delay the event until the user visits the site next time.

I'm not sure the user would manually regrant the permission in general, one would usually do it from the prompt triggered by the website, so unclear whether firing the event on regrant is worth doing.

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

Message ID: <w3c/push-api/pull/400/c2821300483@github.com>