1957195 - Add a way for websites to cancel old push messages

Status: NEW

(Core :: DOM: Push Subscriptions, enhancement)

Description

[Jeff]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0

Steps to reproduce:

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.

Actual results:

Notifications aren't dismissed after being actioned on another device and take several minutes to clear.

Expected results:

Don't show old notifications, or group them allowing them to be dismissed in bulk not one after the other.

Comment 1

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

It should be the website's decision to decide what's an outdated notification that should be removed or not. Unfortunately there's no way for website to mark a notification outdated. Filed https://github.com/w3c/push-api/issues/399.

(Firefox cannot and must not know whether a push notification is already outdated or not, because each push message is fully encrypted that the Firefox push server won't know what's in there. It's only visible when until the user receives it.)

Comment 2

[Ina Popescu, Desktop QA]

Thank you for filing this request. Updating the status to NEW based on the explanation in Comment 1.