Hide Forgot
Description of problem: If I launch Nautilus and select one or more files and press delete, nothing happens. I have to right-click and select "Move to Trash" from the context menu. Version-Release number of selected component (if applicable): nautilus-3.0.0-1.fc15.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Launch Nautilus. 2. Select some files with the mouse. 3. Press delete. Actual results: Nothing happens. Expected results: Files should be moved to trash. Additional info:
The keyboard shortcut has been changed to Ctrl-Delete in the 3.0.0 release.
A release not entry has been added to: https://fedoraproject.org/wiki/Documentation_Desktop_Beat#How_do_I_delete_a_file.3F
1. This makes it seem like the user's delete key is broken, or suspect. The response is to press it again, but harder. Misusing the standard keyboard "delete" key is definitely a user frustration that will lead to annoyance with the change. (eg does the delete keys in-action propagate through every application on the desktop ? Does she need to press ctrl-delete in email and wordprocessing ?) 2. Since both the versions of delete: - move to trash - delete now require modifier keys, and those modifiers are located immediately next to each other on the keyboard, we have just introduced an additional user interface fault where the user intends to delete to trash, but activates the delete permanently command instead. 3. The right click of selected item context menu does not show the shortcut keys available to use for any menu item. So now the user who knows that they need to press a modifier to make normal delete to trash work, can't be helped by the user interface in performing that action, and will (2) get it wrong. 4. If such change is intended to be permanent, perhaps the delete button alone should show a information dialog describing the change, the new shortcut key, with an "OK, I get it, don't tell me again" checkbox.
*** Bug 699397 has been marked as a duplicate of this bug. ***
*** Bug 704107 has been marked as a duplicate of this bug. ***
*** Bug 706767 has been marked as a duplicate of this bug. ***
*** Bug 709457 has been marked as a duplicate of this bug. ***