Bug 466844 - Wayland: Windows marked "keep on top" cover up panel widget pop-ups and clipboard history menu
Summary: Wayland: Windows marked "keep on top" cover up panel widget pop-ups and clipb...
Status: RESOLVED DUPLICATE of bug 476080
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.27.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-04 18:41 UTC by Naxdy
Modified: 2023-12-13 21:37 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Naxdy 2023-03-04 18:41:45 UTC
SUMMARY
When opening the clipboard history on a window that has been set to "Keep above others", the clipboard history opens behind that window, instead of above it, leaving it inaccessible by mouse.


STEPS TO REPRODUCE
0. Log in to plasma wayland
1. Open any GUI application with a server-side decoration
2. Right click the decoration > more actions > check "Keep above others"
3. Position your mouse cursor near the edge of the window.
4. Open the clipboard history using Meta + V

OBSERVED RESULT
Clipboard history opens behind the window

EXPECTED RESULT
Clipboard history opens above the window

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo
(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
This bug would probably be an easy fix, by simply setting the clipboard history to always "Keep above others", as then it would have priority while focused (and since it closes itself when unfocused anyway, this would be sufficient imo).
Comment 1 Nate Graham 2023-03-06 23:20:00 UTC
IIRC it's a generic issue on Wayland. The same happens to panel popups; they open behind "keep on top" windows
Comment 2 Oliver Beard 2023-10-25 13:03:42 UTC

*** This bug has been marked as a duplicate of bug 462181 ***
Comment 3 Nate Graham 2023-12-13 21:37:47 UTC

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