1313376 - Regression: Gecko does not emit accessible keyboard events after an AT is terminated and restarted

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Joanmarie Diggs]

Attachment: accessible-event listener: keyevents.py

Steps to reproduce:
1. Launch the attached accessible-event listener in a terminal
2. Launch Firefox and give it focus
3. Press several keys (e.g. type "hello" in the search entry)
4. Press F4 to terminate the listener
5. With Firefox still running, restart the listener
6. Give focus to Firefox and repeat steps 3 and 4

Expected results: The keys pressed during step 6 would be printed in the terminal. Upon pressing F4, the listener would be terminated. (In other words, the results of step 6 should be the same as the results of steps 3 and 4.)

Actual results: None of the keys pressed during step 6 are printed in the terminal and pressing F4 from within Firefox fails to terminate the listener.

To work around this regression, one can quit and restart Firefox.

Works as expected through: 52.0a1 (2016-09-26) (64-bit)
Broken beginning with: 52.0a1 (2016-09-27) (64-bit)
Possible regression of bug 1204171?
Happens regardless of whether or not e10s is enabled.

Marking severity as "major" because Orca relies upon keyboard event notification to perform commands (including all the commands for navigating and reading documents).

Comment 1

[Trevor Saunders (:tbsaunde)]

Attachment: reinstall the key event snooper when necessary

If we unregister the last key event listener we will uninstall the key event
snooper, so we need to reinstall it when a new key event listener is added.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f686f5590975
reinstall the key event snooper when necessary r=davidb

Comment 3

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/f686f5590975