1728437 - Don't populate entries in cache for absent/default fields

Status: RESOLVED FIXED

(Core :: Disability Access APIs, enhancement)

Description

[Eitan Isaacson [:eeejay]]

For example, only a fraction of accessibles in a document will have a name. We shouldn't need to push or store empty name/nameflag entries for those accessibles. Also, if an accessible loses a name, or any field, there should be a way to remove that entry from the cache instead of populating the cache with an empty field.

This will be even more important when caching description or text values - only a tiny fraction of accessibles have those.

Comment 1

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1728437 - Keep cache sparse and only store populated fields. r?Jamie

When constructing the initial cache, don't push empty or default fields.
Also, have a way to remove fields from an established cache if it
becomes empty/default.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/b45c8e1007d7
Keep cache sparse and only store populated fields. r=Jamie

Comment 3

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/b45c8e1007d7