Bug 460350 - If a notification is kept in the history, shouldn't 'resident' be the default mode?
Summary: If a notification is kept in the history, shouldn't 'resident' be the default...
Status: RESOLVED DUPLICATE of bug 459774
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.25.5
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-13 10:25 UTC by Gabriel Rodrigues
Modified: 2022-10-13 12:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel Rodrigues 2022-10-13 10:25:22 UTC 
SUMMARY

If a notification don't has the transient or resident hint, but it's being kept in history shouldn't it conserve it's intractable capabilities, as a resident would do? Or at least, shouldn't have a place where we could choose to make resident the default behavior?

STEPS TO REPRODUCE
1. Receive a clickable notification, from like, Telegram.
2. Let it go to the history.
3. Open the notification history.

OBSERVED RESULT
The notification loses it's interactive capabilities. Once you click it, nothing happens.

EXPECTED RESULT
If the notification is being kept in the history, as a resident notification would, it also should kept it's interactive properties.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.19.13-arch1-1/5.25.5
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Comment 1 Bug Janitor Service 2022-10-13 10:34:15 UTC 
Thank you for the bug report!

Please note that Plasma 5.25.5 is not supported for much longer by KDE; supported versions are 5.24, and 5.26 or newer.

If at all possible please upgrade to a supported version and verify that the bug is still happening there.
Comment 2 Nicolas Fella 2022-10-13 12:20:08 UTC 

*** This bug has been marked as a duplicate of bug 459774 ***