After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 727693 - Message dialogs are decorated twice (window manager and client-side)
Message dialogs are decorated twice (window manager and client-side)
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: CSD
 
 
Reported: 2014-04-06 04:35 UTC by John Lindgren
Modified: 2014-08-03 18:48 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot (15.53 KB, image/png)
2014-04-06 04:35 UTC, John Lindgren 		Details

Description John Lindgren 2014-04-06 04:35:36 UTC 
Created attachment 273645 [details]
Screenshot

When GTK+ 3.12 is used outside of GNOME, GtkMessageDialogs are decorated twice -- by the X11 window manager *and* client-side by GTK+.  See attached screenshot from XFCE.

Documentation for the "gtk-dialogs-use-header" property says, "This setting does not affect custom dialogs using GtkDialog directly, or message dialogs."  I am not sure why message dialogs should be treated as a special case; but whatever the intent was, the result is ugly.
Comment 1 John Lindgren 2014-04-06 17:17:24 UTC 
Actually, this is not specific to GtkMessageDialog, other GtkDialogs are doing it as well.  Seems that xfwm4 treats GDK_DECOR_BORDER the same as GDK_DECOR_ALL.
Comment 2 Matthias Clasen 2014-04-07 12:45:20 UTC 
see https://bugzilla.xfce.org/show_bug.cgi?id=10631
Comment 3 John Lindgren 2014-04-07 15:21:13 UTC 
Sure.  It's clearly an xfwm4 deficiency, so this bug can be canceled.  I would still like a way to disable client-side decorations completely (I am currently patching GTK+ to accomplish that), but I accept that that is a design decision and not within the scope of this bug.
Comment 4 Matthias Clasen 2014-08-03 18:48:47 UTC 
this should be fixed