Bug 448399 - reaching a specific grouped window with mouse can be tricky
Summary: reaching a specific grouped window with mouse can be tricky
Status: RESOLVED DUPLICATE of bug 358930
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager (show other bugs)
Version: 5.23.5
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Eike Hein
Depends on:
Reported: 2022-01-13 21:14 UTC by iodreamify
Modified: 2022-01-13 23:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

recording (429.69 KB, video/x-matroska)
2022-01-13 21:14 UTC, iodreamify

Note You need to log in before you can comment on or make changes to this bug.
Description iodreamify 2022-01-13 21:14:58 UTC
Created attachment 145431 [details]

When 2 or more windows are grouped and i know the one i need is located somewhere to the right(not directly above the grouped icon) my hand first either clicks or mouse overs instinctively on the grouped icon and then tries to go directly to the appropriate window. 

But as soon as i go directly to it the mouse passes over an adjacent icon and the thumbnails disappear. Can the mouse event perhaps ignore the hover over the adjacent element for a few moments so it doesn't trigger the tooltip or can anything else be done about this so it doesn't lose focus immediately?
This is one behavior i believe Windows does better. 

Thanks a lot and sorry if this is a duplicate.

1. Group a few windows together 
2. Hover or click on the groupped icon so the thumbnails appear.
3. Try to go directly to the last window thumbnail on the right passing through an adjacent element(not up and then to the right)

Thumbnails disappear

Mouse moves through the icon successfully and thumbnails do not disappear.

Operating System: Arch Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.0-zen1-1-zen (64-bit)
Graphics Platform: X11
Graphics Processor: Mesa DRI Intel® HD Graphics 3000
Comment 1 Nate Graham 2022-01-13 23:05:00 UTC

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