Bug 425338 - One pixel border is always on the sides of a window, even with borders disabled
Summary: One pixel border is always on the sides of a window, even with borders disabled
Status: RESOLVED DUPLICATE of bug 387775
Alias: None
Product: kwin
Classification: Plasma
Component: decorations (show other bugs)
Version: 5.17.5
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-14 09:05 UTC by Grzesiek11
Modified: 2020-09-24 13:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grzesiek11 2020-08-14 09:05:04 UTC
SUMMARY
There is always a 1px border on right and left sides of a window. It looks like "disable borders" is really "set borders to an invisible 1px".
This prevents from selecting options from sidebars in some programs if you move your mouse to the edge of your screen. Really irritating.

STEPS TO REPRODUCE
1. Settings -> Look -> Program look -> Windows look -> Disable borders
2. Install any program that has a sidebar (Thunderbird should be fine).
3. Move your cursor to the edge of screen, where there is a button on the sidebar.
4. Click.
5. Move your cursor one pixel away from the edge of screen.
6. Click.

OBSERVED RESULT
4 - Nothing happens
6 - Button is activated

EXPECTED RESULT
4 - Button is activated
6 - Button is activated

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.7.0-8.3-liquorix-amd64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 7,7 GiB
Comment 1 Grzesiek11 2020-08-14 09:07:15 UTC
I should also include "2,5" step, "Launch the program and maximize it".
Comment 2 Christoph Feck 2020-09-07 20:06:33 UTC
Probably a duplicate of bug 387775. Please confirm if it only affects the left edge.
Comment 3 Vlad Zahorodnii 2020-09-24 13:14:20 UTC

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