GNOME Bugzilla – Bug 106545
Suggestion for keynav editing
Last modified: 2014-03-24 02:35:25 UTC
In light of the recent decision to remove click-to-edit for icon names from nautilus, a more consistent keynav model for the treeview control might be: Space = double-click selected row Enter = Space :) F2 = edit selected cell with all editable cells having an "Edit" item in their context menus.
> with all editable cells having an "Edit" item in their context menus. The GtkTreeView does not have a context menu of it's own. I don't think the keybinding for row activation should be space, enter sounds much more sane to me. And, possibly we can't make such changes until 3.0.
Space is documented in the user guide as the "do it" key for all other controls, so I believe it would be the right choice here as well. Enter should activate the default button in the dialog, so my "Enter=Space" suggestion above should only actually hold true if there's no default set. As for the menu, yes, I know it doesn't currently have one but there's no reason why it shouldn't :) Cut, Copy, Paste and Edit sound like useful things to have on a popup menu for any cell that supports editing.
Maybe for 2.4. Need opinion from jrb.
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME bug list :)
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs. Filter on "SUN A11Y SPAM" to ignore.
I'm afraid that F2 might interfere with applications already using F2 for something. So, personally, I would rather leave it as it is.
I agree with Calum's comment #2. And we need _some_ keyboard method of initiating edit here, for accessibility. If not a context menu, then we need a key, there's no way around that. The F2 argument would be true of any convenient key, but leaving things as-is doesn't solve the problem, unless I am missing the point somewhere.
closing out ancient bugs