1758811 - Stop using java cache when gecko a11y cache is enabled

Status: RESOLVED FIXED

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

Description

[Eitan Isaacson [:eeejay]]

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.

Comment 1

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1758811 - P1: Use gecko cache when it is enabled for retrieving node info. r?Jamie

Comment 2

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1758811 - P2: Deal with lack of cached bundle in SessionAccessibility.sendEvent. r?Jamie

Depends on D140749

Comment 3

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1758811 - P3: Don't push cache when gecko cache is available. r?Jamie

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

Depends on D140750

Comment 4

[Pulsebot]

Pushed by [e-mail]:
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

Comment 5

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/ecc987e8ec17
https://hg.mozilla.org/mozilla-central/rev/0cec1675c395
https://hg.mozilla.org/mozilla-central/rev/1f4a11ecd028