https://bugs.kde.org/show_bug.cgi?id=464090

            Bug ID: 464090
           Summary: Differing interaction with a top Plasma panel on Xorg
                    and Wayland
    Classification: Applications
           Product: yakuake
           Version: 22.12.1
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: h...@kde.org
          Reporter: ja...@nejedli.cz
  Target Milestone: ---

Created attachment 155175
  --> https://bugs.kde.org/attachment.cgi?id=155175&action=edit
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

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to