Closed Bug 1758811 Opened 2 years ago Closed 2 years ago

Stop using java cache when gecko a11y cache is enabled

Categories

(Core :: Disability Access APIs, task, P1)

All
Android
task

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: eeejay, Assigned: eeejay)

References

Details

(Whiteboard: [ctw-m1])

Attachments

(3 files)

There are two more places where the java cache is still used when ctw is enabled:

  1. createAccessibilityNodeInfo is the main way android retrieves nodes in the accessibility tree. When gecko cache is enabled, we should get the node info directly from gecko and skip the java cache.
  2. sendEvent uses the cache to retrieve the class name when none was provided.

Once those two cases are resolved we can also stop pushing a cache to the java layer.

Summary: Use gecko cache when getting nodes via createAccessibilityNodeInfo → Stop using java cache when gecko a11y cache is enabled

This requires a little bit of decoupling of dispatching
WINDOW_CONTENT_CHANGED events when the content changes.

Depends on D140750

Pushed by eisaacson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ecc987e8ec17
P1: Use gecko cache when it is enabled for retrieving node info. r=Jamie
https://hg.mozilla.org/integration/autoland/rev/0cec1675c395
P2: Deal with lack of cached bundle in SessionAccessibility.sendEvent. r=Jamie
https://hg.mozilla.org/integration/autoland/rev/1f4a11ecd028
P3: Don't push cache when gecko cache is available. r=Jamie
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: