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 659926 - GtkFrame shadow types all look the same
GtkFrame shadow types all look the same
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: .General
3.1.x
Other Linux
: High major
: ---
Assigned To: gtk-bugs
gtk-bugs
: 665278 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-09-23 09:31 UTC by gtglus
Modified: 2014-07-10 04:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description gtglus 2011-09-23 09:31:06 UTC 
As discussed in a Gtk+ list thread (21.09.2011), GtkFrame (Gtk+-3.0) shadow types don't work properly according to a given GtkShadowType value. The exact effect that I get is to see the same GTK_SHADOW_IN for each three other values.

I'm working under Gnome 2 + Metacity... but seems not running under Gnome 3, too.
Comment 1 Jean Bréfort 2011-09-23 09:45:15 UTC 
With gtk3 and the Adwaita theme, frames are just not visible, except their associated label. The Adwaita theme actually hides all the gtk <3 3d effects. GtkSeparator is just invisible. Are these widgets deprecated?
Comment 2 Murray Cumming 2011-09-29 11:05:49 UTC 
If a very popular theme ignores the shadow type, shouldn't our documentation give a hint that that might happen?
Comment 3 Sébastien Granjoux 2011-10-15 07:28:10 UTC 
I have reported a similar issue some time ago in bug #642514. I find it quite annoying so I'm ready to help here.

It's a bit worst than just ignoring the shadow type because this property is used outside the theme engine in gtk code. By example the GtkScrolledWindow widget doesn't even call gtk_render_frame if the shadow type is set to GTK_SHADOW_NONE while GtkViewport always call it. So if shadow type is set to GTK_SHADOW_NONE, depending on the widget, the frame will appear or not.

I think the theme engine should at least take care of this.
Comment 4 Emmanuele Bassi (:ebassi) 2011-10-15 08:36:48 UTC 
please, Sébastien: don't change the Bugzilla fields. NEEDINFO is for the the maintainers to set when asking questions to the bug reporter. and this bug is not a crasher, so the 'critical' severity doesn't apply.
Comment 5 Sébastien Granjoux 2011-10-15 08:44:23 UTC 
(In reply to comment #4)
> please, Sébastien: don't change the Bugzilla fields. NEEDINFO is for the the
> maintainers to set when asking questions to the bug reporter. and this bug is
> not a crasher, so the 'critical' severity doesn't apply.

Sorry if I have done it wasn't on purpose.
Comment 6 Matthias Clasen 2014-01-25 03:29:55 UTC 
*** Bug 665278 has been marked as a duplicate of this bug. ***
Comment 7 Matthias Clasen 2014-07-10 04:17:32 UTC 
I've clarified the documentation now.