Bug 425276

Summary: Maximized Firefox goes under an "Always Visible" panel on Wayland
Product: [Plasma] kwin Reporter: Kyrylo Bohdanenko <kirill.bogdanenko>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns, kirill.bogdanenko, Lukas, nate
Priority: NOR    
Version First Reported In: 5.19.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Kyrylo Bohdanenko 2020-08-12 23:10:08 UTC
SUMMARY
When running Firefox (79), it does not respect the panel's "Always Visible" policy and goes under the panel in the maximized mode

STEPS TO REPRODUCE
1. Set MOZ_ENABLE_WAYLAND=1 environment variable to make Firefox run on Wayland
2. Set panel's policy is set to "Always Visible"
3. Maximize Firefox

OBSERVED RESULT
The Firefox's window goes below the panel. And if the panel is at the bottom it hides the "Find In Page" bar.


EXPECTED RESULT
Firefox must not go under the panel when maximized

SOFTWARE/OS VERSIONS
Linux: Kubuntu 20.10 (development branch) 
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION

All the other apps (Qt, GTK and XWayland) respect the panel's policy and do not go under when maximized.

This does not seem to be the same issue as described in 409905.
Comment 1 Patrick Silva 2020-08-21 16:55:53 UTC
On neon unstable, Firefox 79 running natively on Wayland only goes below plasma panel on bottom on opening.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.19.80
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Comment 2 Lukas Spies 2020-09-20 04:49:33 UTC
This seems to affect not only Firefox but also other applications. I have observed it with Dolphin, Konsole, Kwrite, Chromium, Kate, and others. Usually a restore & maximize makes the window respect the panel.

This bug is also still present in 5.19.90.
Comment 3 Patrick Silva 2021-05-14 15:36:37 UTC

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