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 45691 - Scroll region does not reduce when you scroll
Scroll region does not reduce when you scroll
Status: RESOLVED DUPLICATE of bug 43404
Product: nautilus
Classification: Core
Component: Views: Icon View
0.x.x [obsolete]
Other Linux
: Normal normal
: old
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-01-16 20:17 UTC by Brett Neely
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Brett Neely 2001-09-10 00:51:55 UTC
Imagine three icons laid out manually such that they are in a horizontal line,
and spaced too far apart to be visible at the same time.  Scroll over to the
icon on the left side, and drag it just beneath the middle icon.  Scroll to the
far right.  The scrollbar now hides some portion of screen that contains no
icons.  The only way this area will disappear is if the Nautilus window is
resized.

Nautilus needs a way of knowing that all icons within the current directory are
visible, and any scroll regions can be eliminated.  This elimination should be
triggered upon a scroll rest.



------- Additional Comments From sullivan@eazel.com 2001-01-16 15:24:26 ----

There are actually several ways to trigger the elimination of this extra white 
space (one example is Refresh), but it's true that just scrolling will not do 
so.



------- Additional Comments From eli@eazel.com 2001-03-26 11:12:04 ----

QA Assigning to self.



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:51 -------
Comment 1 John Fleck 2002-01-05 04:25:56 UTC
Changing to "old" target milestone for all bugs laying around with no milestone set.
Comment 2 Kjartan Maraas 2002-08-04 15:10:52 UTC
Duplicate.

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