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 766667 - Invisible GtkCellRenderers have strange effect on column size
Invisible GtkCellRenderers have strange effect on column size
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
3.21.x
Other All
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2016-05-19 15:01 UTC by LRN
Modified: 2018-04-15 00:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Testcase (2.98 KB, application/xml)
2016-05-19 15:01 UTC, LRN
Details

Description LRN 2016-05-19 15:01:11 UTC
Created attachment 328207 [details]
Testcase

How to reproduce:
* Open the attached testcase in Glade
* Run preview
* Play with the three gboolean items in liststore to, for example, make only the second renderer invisible in the first row

Expected behaviour:
* Column width is calculated based on width of visible renderers for all of its rows
* Column height is calculated based on height of visible renderers of all of its rows

Actual behaviour:
* When first renderer in the first row is invisible, first row gains huge amounts of height for no apparent reason
* When second renderer (but not the first) in the first row is invisible, the column doesn't get enough width to display the second row completely (second renderer in the second row is ellipsized).
Comment 1 Matthias Clasen 2018-02-10 05:27:24 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:39:36 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new