Bug 444332

Summary: [Wayland] Fullscreen snapping causes incorrect window size in Chromium-based browsers
Product: [Plasma] kwin Reporter: indecisiveautomator
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: minor CC: kde, keith, nate
Priority: NOR    
Version First Reported In: 5.23.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description indecisiveautomator 2021-10-24 16:55:07 UTC 
SUMMARY
Under Wayland, "snapping" a Chromium-based browser window to fullscreen by dragging it to the top of the window results in an incorrectly sized window on Chromium-based browsers. It only affects these browsers when they're running on Wayland (e.g., adding the flags "--enable-features=UseOzonePlatform --ozone-platform=wayland"), and does not affect them under Xwayland. I have tested Chromium, Brave, and Brave Beta.

I am unsure if this affects Electron, as the only Electron based app I use that works with Wayland is Discord (VSCodium causes a system lockup, unable to test). When using the above flags with Discord the issue is not present, it correctly sets window geometry.


STEPS TO REPRODUCE
1. Open a Chromium-based web browser (including standard Chromium)
2. Drag window to the top of the screen to maximise it
3. Window is extended too far to the right and too far to the bottom, cut off from view.


OBSERVED RESULT
When snapping Chromium-based browsers to fullscreen, the window is extended too far to the right and too far on the bottom. However, the window is correctly set to fullscreen. There are no rounded corners, and the maximise button changes to a minimise button.

Double-clicking the window along the top or pressing the maximise button will correctly set the window to fullscreen and correctly set its size. It is only the "snap" action that causes this incorrect sizing.


EXPECTED RESULT
Snapping a window to fullscreen should maximise in the same way as double clicking the window's titlebar or clicking the maximise button.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.14-arch1-1 (64bit)
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Does not appear to affect Electron apps, but may require additional testing.
Comment 1 indecisiveautomator 2021-10-31 06:09:27 UTC 
After additional testing it seems like it does not affect Electron apps that I am using. Perhaps the issue is with Chromium's CSD?
Comment 2 indecisiveautomator 2021-11-02 18:16:50 UTC 
Looks like it's been reported to the Chromium bugtracker: https://bugs.chromium.org/p/chromium/issues/detail?id=1248735#c8
They mention it could be related to this issue, which seems to be fixed as of today: https://bugs.chromium.org/p/chromium/issues/detail?id=1223005

Likely this is an upstream Chromium issue then, and will need to be fixed on their part.
Comment 3 Keith Calvelli 2021-11-27 00:49:27 UTC 
Related to this issue, I think:  if you close the window while maximized, chromium and chromium based browsers (tested with Brave, Vivaldi, Edge and Chromium) will not reopen with wayland enabled (-enable-features=UseOzonePlatform  -ozone-platform=wayland).  Workaround is to open in XWayland, resize the window, close, then start again with Wayland enabled.

I did not notice this behavior with other Wayland compositors.
Comment 4 indecisiveautomator 2022-01-15 22:21:21 UTC 
Still present in 5.23.90.
Comment 5 David Edmundson 2022-01-19 15:25:48 UTC 
>Likely this is an upstream Chromium issue then, and will need to be fixed on their part.
Comment 6 Vlad Zahorodnii 2022-01-19 18:35:15 UTC 
(In reply to indecisiveautomator from comment #4)
> Still present in 5.23.90.

FWIW, that looks like a chrome bug, which is already fixed in beta (chrome 98).