Closed Bug 1728437 Opened 3 months ago Closed 3 months ago

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

Categories

(Core :: Disability Access APIs, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
93 Branch
Tracking Status
firefox93 --- fixed

People

(Reporter: eeejay, Assigned: eeejay)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

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.

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.

Type: defect → enhancement
Pushed by eisaacson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b45c8e1007d7
Keep cache sparse and only store populated fields. r=Jamie
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
Regressions: 1729058
You need to log in before you can comment on or make changes to this bug.