Bug 432586

Summary:	Dead zone in the top left corner - cannot activate kickoff
Product:	[Plasma] plasmashell	Reporter:	Norbert Preining <norbert>
Component:	Application Launcher (Kickoff) widget	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	coucouf, mikel5764, nate, plasma-bugs, rikmills
Priority:	NOR
Version:	5.20.90
Target Milestone:	1.0
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Norbert Preining 2021-02-06 20:16:06 UTC

SUMMARY

If the panel is on top, and has height less than 32px (?) there is a dead zone in the top-left (top edge and left edge) of a few (4?) pixel where the K button does not react to clicks

STEPS TO REPRODUCE
1. switch the panel to the top edge
2. reduce the height to 30px
3. disable hotspot in top left corner
4. move the mouse to the top left and click

OBSERVED RESULT

THe kickoff is NOT activated

EXPECTED RESULT

The kickoff is activated

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.20.90
(available in About System)
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.20.90
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.13

Comment 1 Aurélien COUDERC 2021-02-06 20:55:15 UTC

In fact it depends on various factors like the scaling and the exact size of the panel. For example I’m using 125% and it’s broken when the panel height is in [30px,40px] but neither below or above.
And for 100% it is broken in [44px, 54px].

What seems to happen is that:
- the K menu icon is not scaled continuously but by by notches, I guess to use only available bitmap sizes and have it always crisp
- when the panel is made taller than the immediately smaller icon size that can fit, padding is added around the icon
- the padding is not clickable (neither on the left nor on the top side in fact)

Comment 2 Rik Mills 2021-02-06 22:57:49 UTC

I can also replicate this in Kubuntu 21.04 development release with the 5.21 beta package I uploaded.

Comment 3 Nate Graham 2021-02-06 23:06:59 UTC

Already fixed in the final version thankfully.

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

Comment 4 Norbert Preining 2021-02-06 23:43:21 UTC

Thanks, and sorry for the duplication!

Comment 5 Nate Graham 2021-02-06 23:43:54 UTC

No problem!