<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD" href="https://bugzilla.gnome.org/show_bug.cgi?id=792889#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD" href="https://bugzilla.gnome.org/show_bug.cgi?id=792889">bug 792889</a> from <a href="page.cgi?id=describeuser.html&login=kyle.devir%40mykolab.com" title="Kyle De'Vir <kyle.devir@mykolab.com>"> Kyle De'Vir</a> <pre>(In reply to Daniel Stone from <a href="show_bug.cgi?id=792889#c21">comment #21</a>) > or that the server prefer SSD by default. Doesn't this seem... backwards? Why should clients that don't provide their own headerbars request CSD on SSD-preferring compositors? Shouldn't they be requesting SSD instead? What's the logic here? > That is as intended. You might have to find a slightly older app which > doesn't have a headerbar; as Drew suggested, gtk-demo would be a good start. gtk3-demo renders its own headerbar, so CSD makes sense. gtk3-demo-application, however, doesn't, so SSD should be preferred, no? When I make clients that provide their own headerbars ask for SSD, kwin_wayland draws SSD as it should, but clients that do not provide such, get nothing. Does this suggest a kwin_wayland bug to you, Daniel? Sorry if I'm repeating myself so often, because I'm intensely frustrated trying to figure out what the solution is supposed to be.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>