SUMMARY I use the "No titlebar and frame": Force to "No" window rule to have KWin force server side decorations on some applications which use CSD by default. My rules were working in X11 - KWin would draw the titlebar above the application's CSD and would draw the Breeze theme's window shadows around the edges of the application. But the rules no longer work in Wayland. I've tested that the "Keep above other windows" rule is still applying properly to these applications in Wayland, so there's no issue with window matching. I can apply the rule in the opposite direction to remove SSDs on normal Qt/GTK applications like Konsole, Dolphin, Qalculate. That works fine in all scenarios. So force-removing SSDs works, but force-adding them doesn't. STEPS TO REPRODUCE 1. For an application which uses CSD, add a rule which has "No titlebar and frame" set to "Force: No" 2. Run the application under an X11 session or in XWayland: the rule works. Run the application under native Wayland: the rule has no effect. OBSERVED RESULT When the application is running under native Wayland, the application does not have SSD applied by KWin. SSDs are drawn in X11 or when using XWayland. EXPECTED RESULT The application has server side decorations applied by KWin even in native Wayland. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I tested this with Gnome's Simple-Scan (any other CSD-using Gnome application should also reproduce) and also with some Electron applications. Electron applications will run under XWayland by default, so this needs to be added to the Exec line in their .desktop files to have them use native Wayland: " --enable-features=UseOzonePlatform --ozone-platform=wayland". Possibly related: https://bugs.kde.org/show_bug.cgi?id=429171
This isn't as doable on wayland as it was under X11. The GTK clients will behave differently. We can force a deco, but it'd have a massive margin and then the window contents. Your best bet is to complain to upstream for not supporting the proper standards.
Created attachment 164623 [details] Response to #c1. (In reply to David Edmundson from comment #1) > This isn't as doable on wayland as it was under X11. The GTK clients will > behave differently. We can force a deco, but it'd have a massive margin and > then the window contents. > > Your best bet is to complain to upstream for not supporting the proper > standards. Like this?
*** Bug 470535 has been marked as a duplicate of this bug. ***
(In reply to Nate Graham from comment #3) > *** Bug 470535 has been marked as a duplicate of this bug. *** I strongly believe this needs to be reopened, because what kde@davidedmundson.co.uk explains in https://bugs.kde.org/show_bug.cgi?id=452240#c2 is now what occurs (as demonstrated by https://bugs.kde.org/show_bug.cgi?id=479372#c1) which means the stated thing to prevent being the reason for closing this as intentional has already come to pass. However, this is also the sole issue keeping me on X11 — it's also *the* reason I initially chose to use KDE Plasma, because differentiating between Windows was impossible in Windows. It's an incredibly important accessibility feature for me.
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #4) Another example of where this is problematic is https://wiki.archlinux.org/index.php?title=Talk:DaVinci_Resolve&oldid=806169#c-RokeJulianLockhart-20240416163900-noborderrule=2_doesn't_work_on_Wayland.