| Summary: | [usability] It is not obvious how to unselect a file/folder in the nav | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Gabriel Luong <gabriel.luong> |
| Component: | Client | Assignee: | Gabriel Luong <gabriel.luong> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | libingw, simon_kaegi |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Gabriel Luong
(In reply to comment #0) > In the navigator if you were at the root, and have a folder selected, the > only way to unselect the folder is to do ctrl + click. This would hinder > people from creating new 'projects' if they did not know of the shortcut. > This would also affect users with touch devices. > > Some proposals: > 1) The selection should be removed if clicked outside of any item in the > explorer-tree div. Deselecting the current selection/selections is OK. But remember there is a current "cursor" behind the selection. You can try the same logic in windows explorer. > 2) Toggle selection - clicking on the selected item unselects it We already did this for iPad but other than that I think we should keep the current behavior. There are some sensitive parts in the selection policy. Here is a typical use case for "keyboard only" navigation and selection, using separation of current "cursor" and current selection. Assume you have 5 folders/rows and you want to select the first, third and fifth folders by arrow, CTRL, and space keys. 1.The default selection is on the first row. 2.CTRL+DOWN key twice to move the cursor to the third row while current selection is not changed. 3.Space key to select the third row while the first row remains selected. 4.CTRL+DOWN key twice to move the cursor to the fifth row while current selection is not changed. 5.Space key to select the fifth row while the first and third rows remain selected. 6.Now the 3 rows are selected. Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |