- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Sun, 30 Mar 2025 00:51:55 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 30 March 2025 07:51:59 UTC
saschanaz created an issue (w3c/push-api#399) We got a feature request in https://bugzilla.mozilla.org/show_bug.cgi?id=1957195, which I think is a valid one: > Chess.com is a the primary source for this issue, trigger many notifications by using the website on a secondary device (this can be as simple as playing a daily game) then launch firefox, the queued notifications will start one after the other with no way to dismiss all sometimes taking several minutes to finish. Here, there are two independent push subscriptions managed by one app server, tied to one user account. The app server triggers two push messages for an event, but even if the user got one from either of the subscriptions, there's no way for the app server to cancel another push message for another subscription. Canceling already delivered push notification may be more tricky (would it allow abusing e.g. for effectively no-notification push?) but it still sounds reasonable to cancel a push message that hasn't delivered yet. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/399 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/issues/399@github.com>
Received on Sunday, 30 March 2025 07:51:59 UTC