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 669753 - If I opened Orca preferences dialog, press TAB and some SHIFT+TAB key combinations, unable to navigate the OK button
If I opened Orca preferences dialog, press TAB and some SHIFT+TAB key combina...
Status: RESOLVED DUPLICATE of bug 669986
Product: orca
Classification: Applications
Component: general
3.3.x
Other All
: Normal normal
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-09 15:06 UTC by Hammer Attila
Modified: 2012-02-13 13:49 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Debug file with shows possible why happening this problem (116.93 KB, application/octet-stream)
2012-02-09 15:06 UTC, Hammer Attila 		Details

Description Hammer Attila 2012-02-09 15:06:52 UTC 
Created attachment 207196 [details]
Debug file with shows possible why happening this problem

Dear Developers,

I experienced following bug in Ubuntu 12.04, Orca latest master version:
If I activate Orca GUI preferences dialog, press TAB key and one SHIFT+Tab key combination, if I press again a Shift+TAB key combination, the caret not jumping Ok button.
For example, if I land the general page, press a TAB key. The caret lands right the desktop layout radio button. If I press a SHIFT+TAB key combination, the caret jumps right the general page.
If I press again SHIFT+TAB key combination, the caret jumps the startup profile combo box, not the OK button.
I attached the debug.out file.

Attila
Comment 1 Joanmarie Diggs (IRC: joanie) 2012-02-13 13:49:23 UTC 
This bug has nothing to do with Orca. Orca is accurately presenting what has focus. It is not changing focus, nor does its GUI do anything non-standard.

I've filed a bug against Gtk+ for this issue.

*** This bug has been marked as a duplicate of bug 669986 ***