[Wayland-bugs] [Bug 792889] On kwin_wayland, non-CSD GTK3 applications started with GDK_BACKEND=wayland *always* request CSD when they shouldn't
gtk+ (GNOME Bugzilla)
bugzilla at gnome.org
Tue Feb 20 08:14:57 UTC 2018
https://bugzilla.gnome.org/show_bug.cgi?id=792889
Fabian Vogt <fvogt at suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fvogt at suse.com
--- Comment #28 from Fabian Vogt <fvogt at suse.com> ---
(In reply to Drew DeVault from comment #25)
> Sorry, what do you expect from me? So far as I can tell Sway and GTK+ are
> both behaving as expected.
GTK currently violates the decoration management protocol, which leads to the
WM assuming that it uses CSD, but GTK assuming that it has SSD -> no decoration
at all.
The protocol says:
If the client does not create a server-side decoration object for
a surface the server interprets this as lack of support for this
protocol and considers it as client-side decorated. Nevertheless a
client-side decorated surface should use this protocol to indicate
to the server that it does not want a server-side deco.
Which means that calling default_mode and getting SSD back is not enough, it
needs to be followed by a request_mode(SSD) call.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20180220/10dcb8a1/attachment.html>
More information about the wayland-bugs
mailing list