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 622812 - Firefox: Combo boxes cannot be activated via cursor routing keys
Firefox: Combo boxes cannot be activated via cursor routing keys
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: braille
2.31.x
Other All
: Normal normal
: 2.32.0
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2010-06-26 17:10 UTC by rudolf.weeber
Modified: 2010-09-20 10:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
portion of a debug.out captured while reproducing the problem (5.79 KB, application/octet-stream)
2010-06-27 02:21 UTC, Joanmarie Diggs (IRC: joanie) 		  Details
probable fix (3.14 KB, patch)
2010-06-27 03:54 UTC, Joanmarie Diggs (IRC: joanie) 		committed Details | Review

Description rudolf.weeber 2010-06-26 17:10:20 UTC 
Hi,
in Firefox, comboboxes do not get activated when clicking on them via the routing keys. Rather, you have to click a few word before the combobox and press tab to activate it.

Regards, Rudolf
Comment 1 Joanmarie Diggs (IRC: joanie) 2010-06-27 02:21:49 UTC 
Created attachment 164725 [details]
portion of a debug.out captured while reproducing the problem

The attached shows what happens after I Tabbed to the 'Product' link on this page and then clicked on the combo box via a cursor-routing key.

Visually what happens is that the combo box expands. I can confirm that focus is not moved there, but rather remains on the link. If we had the proper events (e.g. an object:state-changed:expanded on the combo box), I *believe* we could just do a grab focus and be set. Unfortunately, the only event I'm seeing is an object:state-changed:showing event for an object of ATK_ROLE_WINDOW. That's not especially helpful.

I'll dig into the problem some more, and pull firefox nightly, but I think this is going to wind up being another blocked bug that we need the Mozilla guys to fix.
Comment 2 Joanmarie Diggs (IRC: joanie) 2010-06-27 02:58:27 UTC 
Same deal with the nightly for 3.7a6pre.
Comment 3 Joanmarie Diggs (IRC: joanie) 2010-06-27 03:54:45 UTC 
Created attachment 164727 [details] [review]
probable fix

I was thinking about things in the reverse/wrong order: grabFocus first and then route; not wait for some event and then grabFocus. Silly me. :-)

This solves the problem for me. How 'bout you, Rudolf?