<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><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#c23">Comment # 23</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 <span class="vcard"><a href="page.cgi?id=describeuser.html&login=daniel%40fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> <span class="fn">Daniel Stone</span></a>
</span></b>
<pre>(In reply to Kyle De'Vir from <a href="show_bug.cgi?id=792889#c22">comment #22</a>)
<span class="quote">> (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?</span >
Yes, I misspoke. In this order:
If the client demands CSD (e.g. has a headerbar), CSD will be used regardless
of server preference.
If the server prefers SSD and the client has not demanded CSD, SSD will be
used.
Else, CSD will be used.
I don't know KWin or GTK+ well enough to answer your other questions, I'm
afraid.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>