Bug 386735 - Task manager icons no longer respect Fitt's Law
Summary: Task manager icons no longer respect Fitt's Law
Status: RESOLVED DUPLICATE of bug 387775
Alias: None
Product: plasmashell
Classification: Plasma
Component: Icons-only Task Manager (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-11 05:50 UTC by Nate Graham
Modified: 2017-12-13 17:38 UTC (History)
2 users (show)

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


Attachments
Video illustrating the issue (967.35 KB, video/webm)
2017-11-11 05:55 UTC, Nate Graham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2017-11-11 05:50:30 UTC
As of Plasma 5.10.x, there is now a one-pixel boundary right against the screen edge where task manager icons do not highlight and are not clickable. Unfortunately, these are the "biggest" pixels from the perspective of Fitt's Law--and the easiest to hit.

Correct behavior was observed in 5.9.5, but I upgraded my main machine to 5.10.5 tonight (via Kubuntu 17.10) and noticed this regression. It seems to still be present in git master on KDE Neon.
Comment 1 Nate Graham 2017-11-11 05:55:25 UTC
Created attachment 108782 [details]
Video illustrating the issue
Comment 2 Eike Hein 2017-11-12 07:57:30 UTC
Do you use a non-default theme?

This is most likely a rounding issue causing the buttons to be 1px not tall enough. It's not generally true.
Comment 3 Nate Graham 2017-11-12 14:08:50 UTC
No, I use the standard Breeze theme. And the issue is reproducible at all widths, i.e. no matter how I resize the Icons-Only Task Manager panel, this still happens.
Comment 4 Kai Uwe Broulik 2017-11-12 14:14:04 UTC
Looks like KWin's screen edge interfering. I had that in the top left corner due to a spurious touch screen edge being registered. Any chance of trying it on 5.11?
Comment 5 Nate Graham 2017-11-16 14:08:22 UTC
Yes, turning off the screen edge and rebooting fixes it on 5.10.5. Can't test on 5.11.x right now, sorry. Should we close this as FIXED or a duplicate of something already fixed?
Comment 6 Nate Graham 2017-11-18 18:52:25 UTC
Can't repro on 5.11.3.
Comment 7 Nate Graham 2017-12-13 17:38:07 UTC

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