Lots of notifications seem poorly designed in that nothing happens when you click on them. The notification doesn't get dismissed, nor is any action invoked. What's worse is that some of them stick around for a while before disappearing. To dismiss them you have click on the tiny x in the popup, which is not ideal. I wonder if KDE can do anything to address this problem caused by these third-party notifications Ideally there'd be a shortcut to invoke some default action on the notification, or if none exists, close the popup. I think it may even be a good idea to make sure that clicking on the body of the notification behave the same way as this proposed shortcut (invoke an action if one exists, close as fallback). In rare cases you want to copy notification text, so you might want an escape hatch for this click to dismiss action. Might it be possible to provide a "select text" button on the notification for these purposes? I am not sure whether this is whithin the realm of possibility or will have unwanted side-effects, so at a minimum I would just propose having a standard shortcut to dismiss (and maybe another one to snooze, if that's ever planned as a feature).
"I think it may even be a good idea to make sure that clicking on the body of the notification behave the same way as this proposed shortcut" This would be especially relevant for new users who aren't familiar with the shortcuts.
some of them wont even close when you act on them - like chromium notifications
alternatively it could be closable by a 2 finger swipe to the left on a touchpad which is treated as a left scroll. it already closes on swiping left on a touchscreen like on android. swiping right could pin it, save it for later or perform an action. alternatively a double click could be used to close as well. the middle click could be used for alternative actions. notifications with 2 or more options could use swiping left or right for the major 2 options and indicate that possibility with arrows on the buttons
> What's worse is that some of them stick around for a while before disappearing. To dismiss them you have click on the tiny x in the popup, which is not ideal. This is a separate issue; see Bug 413203. > some of them wont even close when you act on them - like chromium notifications This is still another separate issue; see Bug 464982.
The challenge is: what's sensible? If the app is running, we can focus and raise its window. But what the window is showing may not be relevant to what the notification was about. In this case, is it really sensible? The same goes double if the notification is in the history and the app isn't running anymore: all we can do is launch the app, but then there's no guarantee that the view it shows on launch will be related to the contents of the notification. What would folks propose we do here?