Bug 464455 - Don't wrap when switching tasks by scrolling
Summary: Don't wrap when switching tasks by scrolling
Status: RESOLVED DUPLICATE of bug 404781
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (other bugs)
Version First Reported In: 5.26.4
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-18 13:57 UTC by John Veness
Modified: 2025-09-09 17:32 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Veness 2023-01-18 13:57:13 UTC
STEPS TO REPRODUCE
1. Have, say, three windows open
2. Place the mouse pointed on the task manager bar
3. Scroll the mouse wheel down twenty clicks

OBSERVED RESULT
A "random" window will be selected (depending on which window was first selected).

EXPECTED RESULT
The first (leftmost) window will be selected.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230116
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.4-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620
Manufacturer: HP
Product Name: HP ProBook 450 G4

ADDITIONAL INFORMATION
Maybe this is a personal preference, but I would like the mouse wheel cycling to stop at either end, rather than (as currently) it wrapping around. That would make it act more like the way the mouse wheel works when scrolling a document or web page, or when using it to change volume when hovering over the speaker icon in the notification area, for example.
Comment 1 AndyKluger 2025-09-09 17:32:15 UTC
Looks like https://bugs.kde.org/show_bug.cgi?id=404781

There's a MR and ongoing discussion at https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2377

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