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 167189 - File chooser can't auto-resize properly when scrolling fast
File chooser can't auto-resize properly when scrolling fast
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.6.x
Other All
: Normal normal
: Need diagnosis
Assigned To: gtk-bugs
Federico Mena Quintero
filechooser-retest-and-triage
Depends on:
Blocks:
 
 
Reported: 2005-02-12 19:05 UTC by Yury Puzis
Modified: 2018-04-15 00:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Yury Puzis 2005-02-12 19:05:25 UTC 
Please describe the problem:
If one scrolls through list of files (which should include images of various
sizes, and non-images) very fast (holding the down key) the window starts to
resize incorrectly. 
When 'down' key is released, window ends up either too wide or too thin or
sometimes of a original size.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Yury Puzis 2005-02-12 19:07:33 UTC 
I should add that in order for the effect to take place, file chooser should be
openned for looking up an image (like when adding a background image f.e.). Then
wherever an image is selected, it will appear on the right.
Comment 2 Federico Mena Quintero 2005-06-15 01:39:04 UTC 
See also bug #300334
Comment 3 Federico Mena Quintero 2007-01-24 19:45:58 UTC 
Does this still happen with gtk+ 2.10.x?
Comment 4 Yury Puzis 2007-01-24 22:35:09 UTC 
It does still happens. I am using Ubuntu Edgy right now. It doesn't happen when scrolling slow. Speed is what breakes it.
Comment 5 Matthias Clasen 2018-02-10 05:25:52 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 6 Matthias Clasen 2018-04-15 00:35:40 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