Closed Bug 1782146 Opened 2 years ago Closed 2 years ago

[CTW] Correctness fixes for remote HyperText offsets cache

Categories

(Core :: Disability Access APIs, defect)

defect

Tracking

()

RESOLVED FIXED
105 Branch
Tracking Status
firefox105 --- fixed

People

(Reporter: Jamie, Assigned: Jamie)

References

Details

(Whiteboard: [ctw-m3])

Crash Data

Attachments

(1 file)

There seem to be a few instances where the HyperText offset cache is out of sync with the tree; e.g. bug 1781169, bp-7598590f-d4cd-4832-bf42-b0b340220720. I've found a few places where we're not invalidating the cache where we should, so I'll fix those here in the hope that it addresses these problems.

  1. When we receive text for a text leaf, even for an initial cache push. Previously, we only did this for a cache update. However, a client call could arrive between the tree push and the initial cache push, resulting in an incorrect offsets cache.
  2. When an Accessible is moved. Previously, if a client queried an Accessible while it was being moved or if an Accessible had children before the move but no children after, the cached HyperText offsets could be invalid.
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7f100ad7b6e8
Invalidate the HyperText offset cache for RemoteAccessible in some additional cases. r=eeejay
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
Crash Signature: [ mozilla::a11y::HyperTextAccessibleBase::TextSubstring ]
Crash Signature: [ mozilla::a11y::HyperTextAccessibleBase::TextSubstring ] → [ @mozilla::a11y::HyperTextAccessibleBase::TextSubstring ]
Crash Signature: [ @mozilla::a11y::HyperTextAccessibleBase::TextSubstring ] → [@ mozilla::a11y::HyperTextAccessibleBase::TextSubstring ]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: