Closed Bug 1900668 Opened 1 year ago Closed 1 year ago

Already running Firefox is not accessible when Orca is started

Categories

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

All
Linux
defect

Tracking

()

RESOLVED FIXED
131 Branch
Tracking Status
firefox131 --- fixed

People

(Reporter: eeejay, Assigned: eeejay)

References

Details

Attachments

(1 file)

If Orca is started after Firefox, Firefox does not detect the platform's accessibility state change and a11y is not instantiated. We need a more robust way to start a11y in Linux Firefox mid-session.

Summary: Firefox is not accessible when Orca is started → Already running Firefox is not accessible when Orca is started

Also, listen for changes in IsEnabled property.

Duplicate of this bug: 1601840
Flags: needinfo?(jteh)
Flags: needinfo?(eitan)
Flags: needinfo?(jteh)

This patch is on hold. Trying to figure out a memory leak, not sure if it is legit or not.

Flags: needinfo?(eitan)

There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:eeejay, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.

Flags: needinfo?(jteh)
Flags: needinfo?(eitan)
Flags: needinfo?(jteh)
Flags: needinfo?(eitan)
Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/de9fbd4835b7 Use GDBusProxy for platform a11y enabled check. r=Jamie

Backed out for causing mochitests leakchecks failures.

Flags: needinfo?(eitan)
Flags: needinfo?(eitan)
Pushed by smolnar@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/3a363f963d5c Use GDBusProxy for platform a11y enabled check. r=Jamie
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch
QA Whiteboard: [qa-131b-p2]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: