[plasmashell] [Bug 506633] Notifications with actions never close upon expiry even when they don't go to history
https://bugs.kde.org/show_bug.cgi?id=506633 --- Comment #5 from Nate Graham --- Yeah, that sounds reasonable to me. If you'd like to have a go at implementing that, please feel free! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 506633] Notifications with actions never close upon expiry even when they don't go to history
https://bugs.kde.org/show_bug.cgi?id=506633 Nate Graham changed: What|Removed |Added CC||[email protected] ||t -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 506633] Notifications with actions never close upon expiry even when they don't go to history
https://bugs.kde.org/show_bug.cgi?id=506633 --- Comment #4 from Martin --- Current status is *horrible*. I was controlling notifcations from the app, to not send more than one if one already exists, Plasma 6.4 completely broke that functionality. Now I have to rely on timeout of the notification and assume it was closed then, but that does not hold true, user can hover over the notification, or be in Do Not Disturb where the notifications do not expire. I think a solution here, provided this behavior is desired to be kept, would be to respect things that do not end up history, and developers could then use the "transient" hint to avoid this tar trap. https://specifications.freedesktop.org/notification-spec/latest/hints.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 506633] Notifications with actions never close upon expiry even when they don't go to history
https://bugs.kde.org/show_bug.cgi?id=506633 Nate Graham changed: What|Removed |Added Keywords||regression CC||[email protected] Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Severity|major |normal --- Comment #3 from Nate Graham --- We can probably special-case this to expire notifications that won't end up in the history, but I'm not sure if that might be more confusing for developers than the status quo. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 506633] Notifications with actions never close upon expiry even when they don't go to history
https://bugs.kde.org/show_bug.cgi?id=506633 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #2 from [email protected] --- Notifications that are not shown in the history seem to have just been hidden. You can make them visible in the history through this setting: https://forum.manjaro.org/t/no-notification-history/142344/5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 506633] Notifications with actions never close upon expiry even when they don't go to history
https://bugs.kde.org/show_bug.cgi?id=506633 --- Comment #1 from Martin --- To add some context - my application waits for the close event to send another notification, to not spam them. I have added a workaround in my code to ignore the notification state and only rely on the timer (which is wrong, as the notification can be interacted with and expiry will be longer). The current state will still send hundreds/thousands of close events upon closing of my app, none of which are in the notification history. -- You are receiving this mail because: You are watching all bug changes.
