- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Mon, 28 Apr 2025 06:24:40 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 28 April 2025 13:24:44 UTC
saschanaz left a comment (w3c/push-api#400) > 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? Yeah, just not sure there can be more than one change for a push subscription after initial subscription - namely unsubscription. And not sure firing it for anything else would be web compatible given existing callers may think all events indicate unsubscription (and proceed to ping the app server to unsubscribe). What other changes do you expect? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/400#issuecomment-2835238358 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/pull/400/c2835238358@github.com>
Received on Monday, 28 April 2025 13:24:44 UTC