Bug 468475

Summary: Clickable target of logout widget is smaller than the target for other panel widgets
Product: [Plasma] plasmashell Reporter: Adam Fontenot <adam.m.fontenot+kde>
Component: Lock/logoutAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 5.27.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: screen recording showing click failures on logout widget

Description Adam Fontenot 2023-04-13 17:23:42 UTC
Created attachment 158075 [details]
screen recording showing click failures on logout widget

SUMMARY

I've been chasing down a mental list of "KDE ate my click!" bugs to reproduce and report them. This manifests as a "logout button ate my click" bug, although that's not actually what happens.

The issue here is that the click target for the logout widget doesn't extend to the screen-edge of the panel. I tested every other widget I have on my panel, and all of them receive the mouse hover and mouse click events when the cursor is at or near the edge of the screen over the widget.

Note: I have a top panel. I don't think that's important to reproduce, but someone with a bottom panel may want to check whether the issue is with the *upper* edge of the widget or the *outer* edge (meaning towards the outside of the screen).

STEPS TO REPRODUCE
1. With a top panel and logout widget, place the cursor close to the screen edge over the widget. (Either directly against the screen edge or one or two pixels away from it).
2. Click the mouse button in an attempt to activate the widget.

OBSERVED RESULT
The logout widget does not activate.

EXPECTED RESULT
The logout widget activates.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.10-arch1-1 (64-bit)
Graphics Platform: X11
Comment 1 Nate Graham 2023-04-13 20:03:03 UTC
Ultimately the same root cause as Bug 467564.
Comment 2 Nate Graham 2023-04-13 20:03:13 UTC

*** This bug has been marked as a duplicate of bug 467564 ***
Comment 3 Nate Graham 2023-09-07 13:42:51 UTC

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