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 735031 - Selected file status bar obscures filenames
Selected file status bar obscures filenames
Status: RESOLVED DUPLICATE of bug 651293
Product: nautilus
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-08-19 03:56 UTC by Ash Kyd
Modified: 2014-08-19 20:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Status bar too long to ever see middle filename (48.49 KB, image/png)
2014-08-19 03:56 UTC, Ash Kyd
Details

Description Ash Kyd 2014-08-19 03:56:54 UTC
Created attachment 283858 [details]
Status bar too long to ever see middle filename

When a file is selected and the status bar appears, it can become long enough that it obscures some filenames. This is especially obvious when the window is small.

This is a problem because when selecting multiple files, it can become difficult to find the files you're looking for.

To reproduce:

1. Open a folder with a large number of files.
2. Click the "View items as a grid of icons" button.
3. Resize the window to show 3 rows of files.
4. Scroll to the bottom of the folder.
5. Select a file at the top of the screen.

At this point the contextual status bar appears, and obscures either the right two, or left two icons. Hovering the status bar moves it to the opposite side of the screen, however if the status bar is long enough it will always obscure the centre icon.
Comment 1 Ash Kyd 2014-08-19 04:00:27 UTC
(3 columns, not 3 rows. I'm not sure I can edit that description.)
Comment 2 André Klapper 2014-08-19 20:41:49 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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