Bug 471130 - Latest notifications should be on top, not on bottom (so you don't have to scroll to see the most recent state of things)
Summary: Latest notifications should be on top, not on bottom (so you don't have to sc...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.27.5
Platform: Other Other
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: usability
: 501645 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-06-16 18:54 UTC by Daniel
Modified: 2025-03-31 16:08 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
example of wrong ordered notification list (63.55 KB, image/png)
2023-06-16 18:54 UTC, Daniel 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel 2023-06-16 18:54:11 UTC 
Created attachment 159720 [details]
example of wrong ordered notification list

SUMMARY
Sometimes (reason is unknown to me) the notifications are displayed in a wrong order in the notification list. Specifically, the latest notification is not on the top. This makes it hard too find the notification if you want to check the latest one.


STEPS TO REPRODUCE
still unknown

OBSERVED RESULT
the latest notification is not always on the top and sometimes an older notification is above an older one.

EXPECTED RESULT
the latest notification should be at the top and the order should be chronological only (if a "grouped" notification is partly dismissed, should the notification go down in the list?)

Operating System: Arch Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.9
Kernel Version: 6.3.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20QGS00A00
System Version: ThinkPad X1 Yoga 4th
Comment 1 Nate Graham 2025-03-29 14:23:46 UTC 
*** Bug 501645 has been marked as a duplicate of this bug. ***