1297456 - about:support claims that a11y is off even though it is on

Status: VERIFIED FIXED

(Core :: Disability Access APIs, defect)

Comment 1

[(No longer employed by Mozilla) Aaron Klotz]

Might this just be because Troubleshoot.jsm is trying to resolve the accessibility service before such a lazy load has been triggered?

Comment 2

[alexander :surkov (:asurkov)]

Yura, have ideas on this?

Comment 3

[Yura Zenevich [:yzen] (please use "needinfo")]

Are there STR's?

Comment 4

[(No longer employed by Mozilla) Aaron Klotz]

Jimm and I have both been able to repro this as follows on today's Windows Nightly:

1) Set browser.tabs.remote.force-enable = true
2) Restart the browser
3) Do something that instantiates a11y (in our case we used our touchscreens)
4) Check the a11y section in about:support

Comment 5

[Yura Zenevich [:yzen] (please use "needinfo")]

OK, thanks.
The way it is checked right now is not valid any more, I will take this as there's a simple way to fix that:
just need to check nsIXULRuntime's accessibilityEnabled attribute instead.

Comment 6

[Yura Zenevich [:yzen] (please use "needinfo")]

Attachment: Bug 1297456 - use nsIXULRuntime's accessibilityEnabled attribute in Troubleshoot.jsm to check if accessibility service is enabled.

Review commit: https://reviewboard.mozilla.org/r/73848/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/73848/

Comment 7

[:Felipe Gomes (needinfo for replies!)]

Comment on attachment 8784385 [details]
Bug 1297456 - use nsIXULRuntime's accessibilityEnabled attribute in Troubleshoot.jsm to check if accessibility service is enabled.

https://reviewboard.mozilla.org/r/73848/#review71712

Cool. It'd be nice to uplift this to at least Aurora.

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/961d542d90a1
use nsIXULRuntime's accessibilityEnabled attribute in Troubleshoot.jsm to check if accessibility service is enabled. r=Felipe

Comment 9

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/961d542d90a1

Comment 10

[Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact [e-mail]]

I reproduced this issue using Fx 51.0a1, build ID: 20160823072522, on Microsoft Surface 2.
I can confirm this issue is fixed, I verified using Fx 51.0b10, build ID: 20161222080852, on Microsoft Surface 2.

Cheers!