Bug 503126 - notifications are not interactive (no onClick() functionality)
Summary: notifications are not interactive (no onClick() functionality)
Status: RESOLVED DUPLICATE of bug 405639
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (other bugs)
Version First Reported In: 6.3.4
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-21 16:59 UTC by lfritzsche1990@gmail.com
Modified: 2025-04-21 22:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented 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 lfritzsche1990@gmail.com 2025-04-21 16:59:29 UTC 
SUMMARY

Clicking on a notification wich should start some action results in nothing, its like clicking on nothing at all.
Example: clicking on a notification from discord.
Expected behaviour: Discord should open if not allready, relevant server and channel should open and it should scroll to the message.
Actual behaviour: Nothing, seems like it doesnt even detect im clicking on the notification, as it should automaticall close itself after being clicked on.


STEPS TO REPRODUCE
1. Get a notification which should have an interaction
2. click it
3. observe: NOTHING HAPPENS

OBSERVED RESULT
nothing happens

EXPECTED RESULT
discord opens/other actions specific to whichever application sent the notification

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 62,5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XT
Manufacturer: ASUS

ADDITIONAL INFORMATION
nothing
Comment 1 TraceyC 2025-04-21 22:45:45 UTC 
Thanks for the feature request. This has been requested in bug 405639. I'll add your suggestion there and close this out. Please follow the other report for updates. Thanks.

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