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 673796 - back and forward buttons in nautilus should be left and not right of the location bar
back and forward buttons in nautilus should be left and not right of the loca...
Status: RESOLVED DUPLICATE of bug 662539
Product: nautilus
Classification: Core
Component: [obsolete] Visual Design
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-09 20:36 UTC by Ambroz Bizjak
Modified: 2012-04-09 21:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ambroz Bizjak 2012-04-09 20:36:07 UTC
In Nautilus (3.2.1), the "back" and "forward" buttons are located on the right side of the location bar, just left to the "search" button. This puts them to the far right side of the window.

This is non-optimal; all other often clicked items are on the left and middle part of the window (the sidebar, the folder entries, and the menu bar). Because of this, clicking "back" of "forward" almost always requires moving the mouse a long way.

Therefore, the two buttons should be moved back to the left side of the location bar, or at least a config option added for doing this. However, I really don't see why anyone would want the buttons on the right. Maybe because if they were on the left, they would move the location bar to the right and make is less accessible? The buttons take almost no space, and that's nothing compared to the extra effort needed to click back/forward.
Comment 1 Cosimo Cecchi 2012-04-09 21:30:05 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 662539 ***