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

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

Ah thanks, that definitely was my misunderstanding. I'm sorry.

I feel like it can still boil down to something like "A user agent may fire pushsubscriptionevent at any time when there's a deactivated subscription that hasn't fired pushsubscriptionevent yet"? I think we can generally agree that we want to fire pushsubscriptionchange event eventually, the only question is when, and that can be implementation detail.

BTW, I think we need to revise section 3.3.2 btw, because if we want to fire pushsubscriptionevent any later than when the permission is revoked, this can't always be true for user agent:

> When a [push subscription](https://w3c.github.io/push-api/#dfn-push-subscription) is deactivated, both the [user agent](https://w3c.github.io/push-api/#dfn-user-agent) and the [push service](https://w3c.github.io/push-api/#dfn-push-service) MUST delete any stored copies of its details.

The browser would need to store the subscription data to fire the event later. (Alternatively the event can just have null for oldSubscription, but not sure we'd want to force that.)

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

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