|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
Bug 1297456 - use nsIXULRuntime's accessibilityEnabled attribute in Troubleshoot.jsm to check if accessibility service is enabled.
58 bytes, text/x-review-board-request
|Details | Review|
Might this just be because Troubleshoot.jsm is trying to resolve the accessibility service before such a lazy load has been triggered?
Yura, have ideas on this?
Are there STR's?
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
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.
Assignee: nobody → yzenevich
Status: NEW → ASSIGNED
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.
Attachment #8784385 - Flags: review?(felipc) → review+
Pushed by email@example.com: 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
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
status-firefox51: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
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!
Status: RESOLVED → VERIFIED
status-firefox51: fixed → verified
You need to log in before you can comment on or make changes to this bug.