Bug 460785

Summary: Option for an unread notifications counter on a panel
Product: [Plasma] plasmashell Reporter: Yevhen Popok <xalt7x.service>
Component: NotificationsAssignee: veggero <niccolo.venerandi>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: kde, nate, niccolo.venerandi, qydwhotmail
Priority: NOR Keywords: usability
Version: git-stable-Plasma/5.26   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: tooltip for "Notifications" applet informs about a number of unread notifications

Description Yevhen Popok 2022-10-20 22:22:37 UTC
Created attachment 153067 [details]
tooltip for "Notifications" applet informs about a number of unread notifications

SUMMARY
***
As we've figured out on https://bugs.kde.org/show_bug.cgi?id=460760  proper implementation of "unread notification badges for applications"  is not that straightforward. Apps need to support Unity API ; distros or users should pre-install libunity ; "sandboxed" applications (Flatpak & Snap) need to communicate with libunity on system or pre-package it etc...
So I'm asking for an option which could at least slightly improve user experience in this regard. Currently "Notifications" applet shows a number of unread notifications from history in an information tooltip which reveals on a mouse hover (screenshot attached).
I'd like to see that number on a panel (over, inside, near or instead standard "bell" indicator, whatever design choice KDE VDG would approve). This way increased number could bring user's attention to some missed messages/events. I believe it could be more noticeable than a "shaking" animation (which eventually stops) or a static "bell" icon. Windows 10/11 has this feature so it's probably useful for someone.
***
Comment 1 Fushan Wen 2022-10-21 11:04:10 UTC
Seems reasonable
Comment 2 Bug Janitor Service 2022-10-21 11:34:16 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2242
Comment 3 Nate Graham 2023-04-28 04:56:39 UTC

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