1275513 - Fix and re-enable a few combobox keyboard tests on OSX

Status: NEW

(Core :: Disability Access APIs, defect, P3)

Description

[Mats Palmgren (inactive)]

In bug 1272012 I disabled a few a11y tests for combobox keyboard event
handling on OSX:

accessible/tests/mochitest/events/test_selection.html
accessible/tests/mochitest/events/test_selection.xul
accessible/tests/mochitest/events/test_valuechange.html

I tried to fix them but I couldn't figure out the testing framework
that is used in these tests.

(Bug 1272012 changed the behavior for VK_UP/VK_DOWN on OSX so that it
now opens the dropdown menu if it's closed.)

Comment 1

[Marco Zehe (:MarcoZ)]

(In reply to Mats Palmgren (:mats) from comment #0)
> In bug 1272012 I disabled a few a11y tests for combobox keyboard event
> handling on OSX:
> 
> accessible/tests/mochitest/events/test_selection.html
> accessible/tests/mochitest/events/test_selection.xul
> accessible/tests/mochitest/events/test_valuechange.html
> 
> I tried to fix them but I couldn't figure out the testing framework
> that is used in these tests.
The tests perform some actions (invokers) and then check if certain events were fired for the accessibility consumers. All this stuff lives in accessible/tests/mochitest/event.js.

In an abstract way, we emulate waiting for, and reacting to, accessibility events like screen readers do, just to make sure screen readers actually get the right events, and that we don't fire unexpected events in certain situations, too.

Does this help?