Bug 442916 - Window previews are not clickable for apps in bottom rows
Summary: Window previews are not clickable for apps in bottom rows
Status: RESOLVED DUPLICATE of bug 347041
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager (show other bugs)
Version: 5.21.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-25 00:52 UTC by David
Modified: 2021-10-05 00:33 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David 2021-09-25 00:52:57 UTC
SUMMARY
In the icons-only task manager, if there's enough icons to make them be arranged into two or more rows, then the window previews that pop up when hovering the mouse over an icon will not be usable for windows that are not in the top row.

STEPS TO REPRODUCE
1. Use the icons-only task manager, and open many windows until the icons span more than one row.
2. In one of the applications that lies on a row other than the top one, open many windows so that it would trigger window previews when hovering the mouse over its icon.
3. Hover the mouse over the icon of the app from point 2, and try to switch windows using those previews.

OBSERVED RESULT
Impossible to switch windows, because as soon as the mouse cursor moves to the row of icons directly above (which it has to cross in order to reach the previews from a row other than the first one), the previews disappear.

EXPECTED RESULT
Should keep the window previews there so that it is possible to click them.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-09-27 20:57:53 UTC

*** This bug has been marked as a duplicate of bug 439363 ***
Comment 2 Fushan Wen 2021-10-05 00:33:07 UTC

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