GNOME Bugzilla – Bug 557462
Remember selection when browsing back or forward.
Last modified: 2017-12-19 13:22:22 UTC
remember selected files and folders for the case of return Other information:
Bug 360516 also is about remembering selection in spatial mode.
*** Bug 586064 has been marked as a duplicate of this bug. ***
Using the location-bar buttons in the Save As dialog does retain the selection when using those buttons to move up and down the currently displayed directory. This is not the same as when Nautilus' location-bar buttons are used. Nautilus should work this way the Save As dialog does, in my opinion. Gnome 2.26.1. Nautilus 2.26.2. -- Also see Bug 563009 related to back/forward behavior affected by the location-bar buttons.
*** Bug 563009 has been marked as a duplicate of this bug. ***
Actually, they are not duplicates: Sorry about my comment 6 -- I did not mean to suggest that these are duplicates. Rather, I thought they are related and devs might find that useful. While both to barelateck and forward navigation, Bug 563009 is about the ordering and integrity of path locations and availability of bck/fwd buttons, this bug Bug 557462 is about remembering _selection_ as an attribute of each location in history.
With the revised focus of Nautilus as a power-user's tool, rather than primary view to a user's documents, I think keyboard navigation will become even more prevalent. This bug is one that prevents easy keyboard use: As it stands, a user can easily select a folder, navigate to it, go back in history, but not perform an operation on the previously selected folder. He either has to reselect it with the mouse or by arrow keys/typeahead. Using either of these techniques to reselect the folder diminishes the advantages of using the keyboard in the first place. Arguably, this is also an accessibility problem.
Changing component as part of ongoing bug reorganisation work.
*** Bug 547988 has been marked as a duplicate of this bug. ***
With 3.26 back works, forward does not. Closing as duplicate of 650455. *** This bug has been marked as a duplicate of bug 650455 ***