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

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

> 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.

I guess that is also fine. I don't even think we need to say "hasn't fired yet". I have the impression that basically the event means "something's changed" and that is also how currently it is interpreted by web developers, who just try to resubscribe upon receiving it. Clarifying some circumstances in which it might make sense to fire the event, as this PR does, also seems meaningful though, no?

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

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