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 770182 - Changing the visibility of GtkToolBar contents causes allocation warnings
Changing the visibility of GtkToolBar contents causes allocation warnings
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkToolbar
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-08-21 01:33 UTC by Kai Willadsen
Modified: 2018-05-02 17:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Simple python test case (965 bytes, text/x-python)
2016-08-21 01:33 UTC, Kai Willadsen 		Details

Description Kai Willadsen 2016-08-21 01:33:30 UTC 
Created attachment 333780 [details]
Simple python test case

Reproduced against the current 3.20.x branch HEAD. This is a new regression as of GTK+ 3.20.

The attached test case just shows a GtkToolButton in an idle handler, which triggers the following warning:

(toolbar-item-size.py:23245): Gtk-WARNING **: Allocating size to GtkToolButton 0x55f514e1c270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

There's no visible effect of this on the rendering of the toolbar or its items that I've noticed.

However, there *is* a more serious side-effect, which is that it (somehow, I have no idea how) causes some GtkRange manipulations in a container with a shared GtkGrid parent to do the wrong thing. I do appreciate how bizarre this sounds. My test case is to trigger this warning in Meld and then see GtkTextView.scroll_to_mark() calls silently fail to actually scroll the mark on-screen.
Comment 1 GNOME Infrastructure Team 2018-05-02 17:25:44 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/659.