Bug 441912

Summary: Cannot activate web notifications from the tray
Product: [Plasma] plasma-browser-integration Reporter: Carlos Solís <csolisr>
Component: FirefoxAssignee: Kai Uwe Broulik <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: mwolos, nate
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Showing the current behavior of the notifications on the tray

Description Carlos Solís 2021-09-02 14:57:35 UTC 
Created attachment 141247 [details]
Showing the current behavior of the notifications on the tray

SUMMARY
When a web notification is stored in the tray after the popup timeout expires, it's no longer possible to activate it by clicking it.

STEPS TO REPRODUCE
1. Open Firefox
2. Navigate to a website and generate a web notification. A site like https://www.bennish.net/web-notifications.html can work as a test.
3. Wait until the notification expires (typically this takes around 5 seconds)
4. Go to the notification tray and click on the notification.

OBSERVED RESULT
The notification does not activate when clicked from the tray.

EXPECTED RESULT
The notification should activate from the tray in the same manner as it activates from the popup.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.13.13
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Running on Arch Linux
Comment 1 Carlos Solís 2021-10-17 16:35:59 UTC 
Commenting on this issue with a KDE contributor, I was told that individual apps, quote, ["need to mark their interactive notifications as "resident" and then their UI elements will appear in the notification history view".](https://www.reddit.com/r/kde/comments/qa1hne/comment/hh00tpc/) Is it possible to mark the notifications from the integration plugin as "resident" directly, or is a helper application required on the Plasma side?
Comment 2 Kai Uwe Broulik 2021-10-20 19:41:20 UTC 

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