Plasma 6 git master, Wayland, 200% scaling. STEPS TO REPRODUCE 1. Have a vertical panel on either a left or right screen edge (doesn't make a difference) 2. Edit the panel to change the alignment from "Center" to either "Top" or "Bottom" 3. Maximize a window OBSERVED RESULT The window goes under the panel EXPECTED RESULT The window does not go under the panel
Created attachment 163440 [details] correct behaviour
I can confirm this, I'm on: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380
Created attachment 163441 [details] correct
Created attachment 163442 [details] incorrect (actual) behaviour incorrect (actual) behaviour
Can reproduce, investigating
This seems to me like a design flaw of layer shells; it clearly states in https://wayland.app/protocols/wlr-layer-shell-unstable-v1 that top/bottom aligned panels are to be achieved by setting two screen sides as an anchor, and yet the exclusive area documentation says that when you set two screen sides as an anchor the exclusive area will be ignored and set as 0. Thus, there's currently no way - according to that documentation - to have non-centered panels that still preserve exclusive areas on the border. I'm not sure how much LayerShellQT can deviate from the above documentation, or whether we can make proposals to change it, but this seems to be currently intentional and unfixable
*** Bug 477597 has been marked as a duplicate of this bug. ***
*** Bug 477793 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3715
Git commit 184585264f560b0f6c6b39e01f0a6cdec0ab5698 by Marco Martin. Committed on 26/01/2024 at 12:55. Pushed by mart into branch 'master'. Add a new setExclusiveEdge call in the protocol This can be used to disambiguate the exclusive edge when the anchors are on a corner (so there would be 2 candidates) it's quite quick and dirty mostly to understand if we do want to push for something along the lines (it should at least do a protocol error when the requested edge is not within the anchors) M +1 -15 shell/panelconfigview.cpp M +7 -0 shell/panelview.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/184585264f560b0f6c6b39e01f0a6cdec0ab5698
Git commit 4382935b5de35d6d50e4efe710b36a234101f4b3 by Vlad Zahorodnii, on behalf of Marco Martin. Committed on 26/01/2024 at 13:54. Pushed by vladz into branch 'Plasma/6.0'. Add a new setExclusiveEdge call in the protocol This can be used to disambiguate the exclusive edge when the anchors are on a corner (so there would be 2 candidates) it's quite quick and dirty mostly to understand if we do want to push for something along the lines (it should at least do a protocol error when the requested edge is not within the anchors) (cherry picked from commit 184585264f560b0f6c6b39e01f0a6cdec0ab5698) M +1 -15 shell/panelconfigview.cpp M +7 -0 shell/panelview.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/4382935b5de35d6d50e4efe710b36a234101f4b3