Bug 464090 - Differing interaction with a top Plasma panel on Xorg and Wayland
Summary: Differing interaction with a top Plasma panel on Xorg and Wayland
Status: RESOLVED UNMAINTAINED
Alias: None
Product: yakuake
Classification: Applications
Component: general (other bugs)
Version First Reported In: 22.12.1
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-10 08:56 UTC by Jakub
Modified: 2023-10-23 18:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Shows the difference between Xorg and Wayland, same settings (627.09 KB, image/png)
2023-01-10 08:56 UTC, Jakub
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub 2023-01-10 08:56:03 UTC
Created attachment 155175 [details]
Shows the difference between Xorg and Wayland, same settings

SUMMARY
I have a top panel set to "Windows can cover." On Xorg, yakuake is anchored at the top of the screen and renders over the top of the panel, while on wayland it is anchored below the panel. 

STEPS TO REPRODUCE
1. Set up a plasma panel on the top of the screen and set it to "windows can cover"
2. Open yakuake

OBSERVED RESULT
On Xorg - yakuake is anchored at the top of the sceen, and drops down over the top of the plasma panel
on Waylan - yakuake is anchored at the bottom of the plasma panel (if the panel is 56 pixels thick, the top of yakuake is on pixel 56) This is the same as the behavior when the Panel is set to "Always visible" on both Xorg and Wayland, but differs from the implementation of "Windows can cover" in xorg

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.86-1-LTS
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.
Qt Version: 5.15.7

ADDITIONAL INFORMATION
//This is based of the code and comments in Mainwindow::getDesktopGeometry
This may not be an issue with yakuake, but rather that the plasma shell implementation of the work area differes from the xorg implementation, or that the panel doesn't correctly adjust the work area under the wayland implementation. I don't know how to check if that is the case, and thus cannot confirm if this is the issue
Comment 1 Jakub 2023-01-15 01:50:07 UTC
> //This is based of the code and comments in Mainwindow::getDesktopGeometry
> This may not be an issue with yakuake, but rather that the plasma shell
> implementation of the work area differes from the xorg implementation, or
> that the panel doesn't correctly adjust the work area under the wayland
> implementation. I don't know how to check if that is the case, and thus
> cannot confirm if this is the issue

Sorry, I missread the comments - On wayland, it's not possible to get the work area from KWindowSystem directly, but you can get it through dbus. The issue might be that the workspace written into Dbus is incorrect. I'll try to check it
Comment 2 Dashon 2023-10-16 01:39:48 UTC
I'm also having this issue even with the panel autohidden it still starts with a few pixels in between the top of the screen and the yakuake window. Furthermore. The bottom part of yakuake's window where the tab name is also appears to be cutoff.
Comment 3 Nate Graham 2023-10-23 18:21:26 UTC
I'm afraid the "Windows Can Cover" Panel visibility mode has been removed for Plasma 6 and we aren't planning to bring it back. In its place, we plan to implement an "intelligent auto-hide" or "dodge windows" mode, per Bug 349785. This should hopefully be much better than "Windows Can Cover" ever was, and offer support for its use cases.

Thanks for your understanding!