GNOME Bugzilla – Bug 570524
(ARIA) Issues with Dojo combo box interaction
Last modified: 2009-02-13 19:59:21 UTC
Go to http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/_autoComplete.html?testWidget=dijit.form.ComboBox Try to navigate to/around the combo boxes. Something is very weird. My understanding is that the arrow keys should allow us to move up to and then over combo boxes. To get into the combo box, the user needs to press Tab (right?) and the arrow keys should then work as normal (i.e., as they do if Orca is not being used) to manipulate the combo box. Instead, the arrow keys seem to take you into the combo box and you can cannot use the arrow keys to select items in the combo box. As a test, I go to the first combo box and delete all but the first "C". This brings up a list of choices that I cannot arrow to when Orca is running. Instead, a down arrow takes me to the line below the combo box.
I suspect I know what's up with this. It may be a side effect of a "design decision". I have an appt, but I'll look when I get back.
Created attachment 127945 [details] [review] revision 1 Pylinted. Not yet regression tested. Will, can you please see if this addresses the problems you are reporting? If so, I'll toss the regression tests at it.
Woo hoo! Seems to work fine. Thanks!
And it regression tested nicely. Patch committed to both trunk and the gnome-2-24 branch. Leaving open for now because we need to write a regression test for this and I'm really, really tired. But I'll write the test and check it in tomorrow and then close this bug.
Created attachment 128070 [details] [review] regression test This regression test has been added to trunk. 1. It indicates we're way too verbose. 2. It passes (verbosity aside) 3.0.5. The results in 3.1b2 are different (some less verbosity, some difference in spacing). Keeping this bug open. I'll investigate further tomorrow and see what I can do about the verbosity (first and foremost) and the test reproducibility. *sigh*
The work I'm doing on the uber caret-moved event/isNaviableAria bug is fixing the extra verbosity. Therefore closing this one as FIXED now.