GNOME Bugzilla – Bug 43404
Unused space past icons isn't reclaimed upon scroll
Last modified: 2004-12-22 21:47:04 UTC
To reproduce: (1) Make a Nautilus window in icon view and manual layout mode that contains two icons. (2) Put one icon on the far left side of the window, and another on the far right side. (3) Shrink the window horizontally enough to cause the horizontal scroll bar to appear. (4) Scroll to the right as far as it will scroll. (5) Drag the icon on the right side a little ways to the left, and drop it. At this point the scroll bars will not update, and there will be unused space to the right of the icon you just dragged. (Thanks to fixing bug 42068) (6) Now use the scroll bar to scroll all the way to the left. (7) Now use the scroll bar to scroll all the way to the right. At this point it will look like it did after step 5. There is still unused space to the right of the icon you dragged in step 5. This unused space should have vanished during step 6. (At least, that's what it would have done on the Macintosh, and probably other platforms.) Currently, you can make this unused space vanish by refreshing, or closing and reopening the window, or doing a few other things. The bug here is simply that the scroll in step 6 should have caused this unused and out-of-sight space to vanish. ------- Additional Comments From eli@eazel.com 2000-10-16 20:07:51 ---- Batch-assigning QA ownership of remaining bugs to eli@eazel.com ------- Additional Comments From sullivan@eazel.com 2000-11-28 16:08:31 ---- Deferred a bunch more P5's, after Darin's input. ------- Additional Comments From eli@eazel.com 2001-02-21 11:12:55 ---- QA Assigning to brett. Sorry for the spam. ------- Additional Comments From eli@eazel.com 2001-03-26 11:11:33 ---- QA Assigning to self. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:41 -------
Changing to "old" target milestone for all bugs laying around with no milestone set.
Confirmed in 2.0.x.
*** Bug 45691 has been marked as a duplicate of this bug. ***
Very trivial.
Bug still exists in 2.2.3.
Fixed in 2.6.