Make GetNodeInfo and Pivot methods run safely in Android UI thread
Categories
(Core :: Disability Access APIs, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox102 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
(Whiteboard: [ctw-m1])
Attachments
(3 files)
We currently post tasks synchronously to the Gecko thread. This has been causing lockups in Fenix UI tests (and probably will in TalkBack as well).
We need to safely perform these operations in the UI thread.
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
About pages run in the parent process. In the following patches we will
be performing some operations like pivot and getting node info in the
Android UI thread. We need to assure that "local" content still works
by calling into the gecko thread since we can't use the remote,
thread-safe cache.
Assignee | ||
Comment 2•3 years ago
|
||
We cannot use GeckoBundle anymore because it cannot be constructed in
the UI thread. Instead, have a set of populate methods that take
arguments and set the correct fields in the AccessibilityNodeInfo, or
its optional info objects.
These fields can be called both in the Gecko and UI thread.
Depends on D144894
Assignee | ||
Comment 3•3 years ago
|
||
Depends on D144895
Comment 5•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a7fe140330b1
https://hg.mozilla.org/mozilla-central/rev/29069798c8e3
https://hg.mozilla.org/mozilla-central/rev/f4fc3e2236e5
Description
•