https://bugs.kde.org/show_bug.cgi?id=459774
Bug ID: 459774
Summary: Make "resident" notifications the default.
Classification: Plasma
Product: plasmashell
Version: master
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Notifications
Assignee: plasma-b...@kde.org
Reporter: xna...@hydra-development.net
CC: k...@privat.broulik.de
Target Milestone: 1.0
Created attachment 152491
--> https://bugs.kde.org/attachment.cgi?id=152491&action=edit
Example of how notifications look with "resident" forced to "true"
Currently, a lot of notifications lose some or all of their functionality after
moving from the standalone notification popup into the notification applet.
As I understand, the idea is that if notifications contain a "resident" hint,
indicating to plasma that this functionality should be preserved.
In my opinion, this should be an opt-out rather than an opt-in (as it currently
is).
As it stands, only a very small minority of applications actually opt in to
this functionality. Those that do not are clearly missing functionality once
their notifications move into the applet. This creates a sort of "race against
time", where a user might feel pressured to click on the notification as soon
as possible, or drastically increase notification timeout, lest they will be
unable to navigate to the notification's origin as easily.
Prime examples here are messaging apps such as Slack or Discord, where the
notification is designed to bring you to the relevant chat immediately. Once
this functionality is lost, navigating to the relevant channel can become a
chore, since you will either have to rely on the application's internal
notification system (e.g. Discord's inbox) or even navigate completely
manually.
What adds additional frustration is that Plasma seems to be one of the only
shells that exhibit this behavior. The GNOME shell, as well as the Windows
desktop both preserve full notification functionality even once the initial
popup has been dismissed (be it manually or automatically). This makes Plasma a
clear outlier in this situation.
For experimental purposes, I have compiled my local `plasma-workspace` to
ignore the "resident" hint, and always display the additional functionality.
Without any further modifications, this results in the aforementioned
functionality being restored in form of a button. The label of said button
appears to be different for each application. Discord & Slack use "View",
whereas Thunderbird uses "Activate".
Furthermore, for some applications, the button loses functionality after the
first press, whereas for others, it continues to work indefinitely. As such, if
we decide to enable the "resident" behavior for every app, it would be
appropriate to dismiss the notification automatically once this button has been
pressed, as this behavior would be intuitive anyway.
I've attached some screenshots of my local notification applet with the
"resident" hint forced to "true" for every app. Even in its current state, it
has already improved usability of the notification applet tremendously for me,
and I no longer feel pressured to click on every notification as soon as
possible.
Alternatively, if we do not want to force this behavior for every app, I
suggest making it a user-configurable option either in the applet or system
settings. This way, users can keep the current behavior if they so choose.
--
You are receiving this mail because:
You are watching all bug changes.
