GNOME Bugzilla – Bug 617508
duplicating item in same folder doesn't move focus to correct item
Last modified: 2021-06-18 15:13:25 UTC
I often make a duplicate copy of an item (file or folder) and work on it, for modifications that I will intentionally throw away. Using keyboard shortcuts to duplicate an item leaves the keyboard focus on the original item instead of shifting it to the new item. This means that successive operations without watching the screen will work on the wrong target. This means that some operations following the copy (Enter to open, Ctrl-I) will operate on the newly created item, though a rapid keyboard navigation + an operation will take action on an unexpected item. Worse, try moving the selection with arrow keys during a longer copy process. Upon completion of the copy, the selection will jump to the newly created duplicate, but the keyboard focus will stay on whatever item you happened to be on at that moment. 1. List view in browser window 2. Select an folder ("foo") 3. Ctrl-C to copy, Ctrl-V 4. (optional) move selection with arrow jeys during copy operation Actual: Newly item ("foo (copy)") is selected, original item ("foo") has keyboard focus. If (4), some other item will have keyboard focus. Pressing down arrow will select the newly created item, instead of the one following it. Pressing up arrow will select the item preceding the original item instead of the original item. If (4), predictable (according to how keyboard focus moves) but unexpected (according to which item has the more visible selection drawn) results: some other item will get selection and focus, but it isn't obvious which one unless the user actually looks for keyboard focus before pressing the arrow keys. Expected: New item ("foo (copy)") has both selection and keyboard focus in all cases. Pressing down arrow will select the item following the newly created item. Pressing up arrow will select the the original item.
Confirming. Thanks for the report.
Changing component as a part of bug reorganisation work.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of Files (nautilus), then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/nautilus/-/issues/ Thank you for your understanding and your help.