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 318727 - tree view probably doesn't properly request new size on size reduction
tree view probably doesn't properly request new size on size reduction
Status: RESOLVED DUPLICATE of bug 316689
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.8.x
Other All
: Normal minor
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2005-10-13 00:31 UTC by Alexander “weej” Jones
Modified: 2006-01-14 20:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Alexander “weej” Jones 2005-10-13 00:31:25 UTC 
Please describe the problem:
Try for yourself to see what I mean.

Steps to reproduce:
1. Enter list view
2. Zoom in so that you can scroll
3. Scroll somewhere near the bottom
4. Zoom out


Actual results:
Empty view with an oddly behaving scroll bar. The scrolling widget is very small
at the bottom of the bar.

Expected results:
Viewport to be automatically scrolled up.

Does this happen every time?
Yes.

Other information:
This does not happen in Icon view. When you zoom out it automatically adjusts
your viewport positioning.

Thanks!
Comment 1 Alexander “weej” Jones 2005-11-30 12:00:21 UTC 
I noticed similar behavior in Gaim when contacts sign out. It leaves space at the bottom of the view which vanishes the second you touch the scrollbar. Is this an issue with the list/tree widget?
Comment 2 Christian Neumair 2005-11-30 18:57:28 UTC 
Yes Alex, this is probably a GTK+ issue. Maybe the list view doesn't change its
size request or something :/.
Comment 3 Christian Neumair 2005-11-30 19:02:34 UTC 
Setting title to supposed reason of the problem.
Comment 4 Kristian Rietveld 2006-01-14 20:02:50 UTC 
This sounds really similar to #316689, and I suppose this has been fixed now.  Marking as duplicate.


*** This bug has been marked as a duplicate of 316689 ***