[Wayland-bugs] [Bug 776290] New: GTK_CSD=0 does not disable CSD

[gtk+ (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=776290

            Bug ID: 776290
           Summary: GTK_CSD=0 does not disable CSD
    Classification: Platform
           Product: gtk+
           Version: 3.22.x
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: Backend: Wayland
          Assignee: gtk-bugs at gtk.org
          Reporter: cyphar at cyphar.com
        QA Contact: gtk-bugs at gtk.org
                CC: rob at robster.org.uk, wayland-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 342234
  --> https://bugzilla.gnome.org/attachment.cgi?id=342234&action=edit
gtk3-make-csd-optional.patch

Currently there exists the GTK_CSD environment variable that is checked to
decide whether CSD should be set for a particular window. However, it's used as
a hint rather than as an instruction to an application.

In addition, even if an application does *not* specify it wants to use CSD, if
you're using a backend other than X (such as Wayland) you will *still* get CSDs
on your GTK+3 applications -- even though neither the user nor the application
want it.

IMO the solution is to either always honour GTK_CSD if it's set, or remove the
code that specifically makes Wayland _always_ use CSDs even if the application
did not request to use them.

I've attached my attempt at a patch for this. PTAL. Note that Arch Linux has
their own patch for this as well[1].

[1]:
https://aur.archlinux.org/cgit/aur.git/plain/gtk3-make-csd-optional.patch?h=gtk3-optional-csd

-- 
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/20161219/eed8a7a2/attachment.html>