Open Bug 1849349 Opened 3 years ago Updated 1 month ago

[KDE] Window controls aren't clickable in the edge/corner of the screen on Plasma

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 115
defect

Tracking

()

UNCONFIRMED

People

(Reporter: linus.kardell, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: gtk-severity-sweep-2026-10)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

Steps to reproduce:

Have the window maximized, and have the cursor in the top right of the screen. Same issue occurs in both Firefox 115 and Thunderbird 115. Unknown whether it happens on other DEs.

Operating System: openSUSE Leap 15.5
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.14.21-150500.55.12-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 1700X Eight-Core Processor
Memory: 62.7 Gibyte of RAM
Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2

Actual results:

There is a margin between the window controls and the edge of the screen, so they will not be activated. This differs from most other maximized windows, where the top right of the screen will activate the close button (even though the buttons don't look like they extend that far), and similarly the minimize and restore buttons can be activated from the very top of the screen.

Expected results:

The window controls should be activatable from the very edge of the screen, to make them easier to hit.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Blocks: gtk-kde
Priority: -- → P3
Summary: Window controls aren't clickable in the edge/corner of the screen on Plasma → [KDE] Window controls aren't clickable in the edge/corner of the screen on Plasma
Severity: -- → S3
Whiteboard: gtk-severity-sweep-2026-10
You need to log in before you can comment on or make changes to this bug.