Starting with Plasma 6.4, if an application sends a D-Bus Notify call with a replaces_id pointing to a notification that has already timed out and been moved to the System Tray, Plasma just updates the notification without showing a new on-screen popup.
This causes a lot of inconvenience. Notifications from Google Chrome often arrive this way when an extension calls the chrome.notifications.create method with an empty notificationId. Consequently, after the first notification is hidden in the tray, no further notifications from the same site or extension appear on the screen.
Before Plasma 6.4, when a notification was hidden in the tray, the CloseNotification command was called, so the app no longer used the old notification’s ID and created a new one. Since version 6.4, this behavior has changed, and now the tray notification remains alive, and Google Chrome attempts to overwrite it.
I don’t think this request is worthy of a bug report, so I’m posting it here.
What do you guys think about? Perhaps this behavior should be made configurable for applications?
I guess it depends on whether the specification has anything to say about this.
It could be a bug and then should be reported as such.
Potentially also interesting how other implementations handle it, e.g. GNOME