https://bugs.kde.org/show_bug.cgi?id=453977
--- Comment #2 from Oded Arbel <o...@geek.co.il> --- Vlad, I'm quite confused by your response: 1. This issue is about X11 and not Wayland. I'm not sure of the behavior on Wayland, but I don't think it applies to this issue if the behavior there is as different from X11 as you describe. If you mean to say "Kwin team will not fix this issue on X11 because that platform is deprecated and the team is focusing on Wayland", that is one thing - but I would expect the resolution to be "WONTFIX" and not "NOT A BUG". 2. You said "... on X11, kwin can't force any decoration mode" - which is seems incorrect to me - as kwin rules successfully force the decoration mode for Qt apps, KDE apps, WxWidget apps, Libre Office, Thunderbird and Firefox (surprisingly? IIRC the last two are using GTK). But after investigating the issue a bit more, I think I understand it a bit more and it all probably starts from my misunderstanding of the idea of setting the rule "No titlebar and frame" to "No" and how it interoperates with GNOME client-side decorations and the gtk3-nocsd hack: - It is now my belief that "No titlebar and frame" means that kwin will hide the decorations for windows that assume server-side decoration. Setting it to "No" does not mean "force server-side decoration" (though I think that would have been useful). - GNOME apps request to disable server-side decorations, which kwin will always honor. - gtk3-nocsd disables the request to disable server-side decorations, causing kwin to draw titlebar and frame. - My main problem is actually Google Chrome apps that use "open as a window", which use CSD, aren't affected by gtk3-nocsd and I can't get kwin to draw reasonable borders around them (making their title bar unreadable due to the bad interaction between Google Chrome CSD colors and the Breeze theme). I'm still not sure why kwin refuses to hide the server side decoration when setting "No titlebar and frame" to "Force" "yes", for a GNOME apps loaded with gtk3-nocsd - it sounds like a bug to me, and possibly, relevant to this issue - but I'm actually not that interested in that problem. -- You are receiving this mail because: You are watching all bug changes.
