https://bugs.kde.org/show_bug.cgi?id=389222
Martin Flöser <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In| |5.15
Latest Commit| |https://commits.kde.org/kwi
| |n/792d8404551d18827b08cf7af
| |709dbb3cfbd4d53
Status|REPORTED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Martin Flöser <mgraess...@kde.org> ---
Git commit 792d8404551d18827b08cf7af709dbb3cfbd4d53 by Martin Flöser.
Committed on 31/12/2018 at 06:58.
Pushed by graesslin into branch 'master'.
Honor struts when placing Wayland transients
Summary:
So far transients were placed anywhere on the screen. This behavior was
inspired from X11 where context menus were able to overlap any other
window and use the complete screen area. On X11 context menus and
similar windows are override redirect and thus above all windows managed
by KWin.
On Wayland, though, context menus and similar and windows just like any
other window and thus follow stacking constraints like the parent
window. A context menu is stacked just above it's parent and is
(normally) below any panels. This resulted in problems that context menu
are stacked behind the panel with unreachable options.
This change changes the placement for transients to use the
PlacementArea instead of a screen geometry. Thus the transient does not
render behind the panel. Only in case of a fullscreen the struts are
ignored.
FIXED-IN: 5.15
Test Plan: New test case
Reviewers: #kwin
Subscribers: kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D17826
M +85 -1 autotests/integration/transient_placement.cpp
M +2 -1 placement.cpp
https://commits.kde.org/kwin/792d8404551d18827b08cf7af709dbb3cfbd4d53
--
You are receiving this mail because:
You are watching all bug changes.
