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

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

The points coming up in the discussion are exactly the reasons why I think it makes sense for the spec to leave it to the user agent to decide when it makes sense to fire and when it does not, for example depending on whether the permission change was the result of a user action and how that action was presented to the user.

As a concrete example, the behavior that chromium would like to [implement](https://issues.chromium.org/issues/407523313) is to fire upon re-grant in site settings. That allows users who removed permissions and want to explicitly grant them again to be able to start receiving notifications again. This is also what is already implemented by Gecko, according to what I was able to test.

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

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