After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 542307 - Little suggestion with Orca structural navigation keybindings
Little suggestion with Orca structural navigation keybindings
Status: RESOLVED WONTFIX
Product: orca
Classification: Applications
Component: general
2.23.x
Other All
: Normal enhancement
: ---
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2008-07-10 06:05 UTC by Hammer Attila
Modified: 2008-07-16 21:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Hammer Attila 2008-07-10 06:05:26 UTC
Dear developers!

The new Orca structural navigation extensions with Firefox 3 is very niceful, but some keybinding functions not defined keybinding keys default With Orca application preferences guy with firefox.
This is not a critical problem because the users define the missing keybinding keys, but easyest usability the new structural navigation feature extension if the missing keybindings keys defined default.
My suggestions:
Goes the next button: b
Goes the prewious button: Shift+b
Goes the next check box: x
Goes the prewious check box: Shift+x
Goes the next radio button: r (this conflict goes the next live region function r keybinding, possible modify this for example with g letter?)
Goes the prewious radiobutton: Shift+r (this conflict goes the prewious live region function Shift+r keybinding, possible modify this with for example with Shift+g letter?)
Goes the next combo box: c
Goes the prewious combo box: Shift+c
Goes the next edit box: e (this is not implemented yet)
Goes the prewious edit box: Shift+e (this is not implemented yet)

If anybody found another useful not defined keybinding, please writing my bugreport comment! If can I help writing patch solve this problem, please writing some instructions.

Thanks,

Attila

Other information:
Comment 1 Joanmarie Diggs (IRC: joanie) 2008-07-10 08:35:15 UTC
Thanks for this feedback Attila.

When I was redoing the structural navigation code and added this support in, the decision was made intentionally to not bind the new structures. It would take me all of a few minutes to add bindings to them, so that's not a problem. The question is, is binding them desirable to/beneficial for the user community as a whole?  I could make an argument that it is; I could make another one that it is not.  That's why we have a UI lead. <smile>  Mike, your thoughts please.
Comment 2 Mike Pedersen 2008-07-10 16:23:52 UTC
The thought here was not to tie up lots of keystrokes for different form controls.  

With the creation of new types of web content such as aria and live regions I really felt it was important to leave as much flexibility in the keyboard layout as possible.  
Unless there is a really strong objection I'd like to close this one as "won't fix" 
Comment 3 Willie Walker 2008-07-16 21:09:43 UTC
Thanks for the discussion on this one.  We're going to close this one as WONTFIX as a means to help keep the keybindings less cluttered.  Users will be able to customize the bindings as they wish.  Thanks for your patience with us, Attila!