Closed Bug 1772477 Opened 2 years ago Closed 11 months ago

[CTW] RemoteAccessible probably doesn't handle a move inside a subtree that is being hidden

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
116 Branch
Tracking Flags:
Tracking Status
firefox114 --- wontfix
firefox115 --- wontfix
firefox116 --- fixed

People

(Reporter: Jamie, Assigned: nlapre)

References

(Blocks 1 open bug)

Details

When an Accessible is hidden and not moved, DocAccessibleParent::ShutdownOrPrepareForMove shuts it down. This shuts down the entire subtree. If there were Accessibles in that subtree that were moved at the same time, they would be shut down too, requiring us to re-create them later.

In theory, the most obvious way to reproduce this is a visibility: visible node inside a visibility: hidden subtree, but we currently re-create LocalAccessibles there instead of moving; see bug 1772042. In theory, another way would be to have a container which aria-owns some target and then remove the container, but LocalAccessible currently clobbers the owned target; see bug 1455416.

In short, this problem is currently theoretical until those LocalAccessible bugs are fixed.

Assignee: nobody → nlapre

Fixed by bug 1455416.

Nathan, is there anything else to do here or can we close this? I assume the tests in bug 1455416 should be enough to cover this?

Depends on: 1455416
Flags: needinfo?(nlapre)
Blocks: 1638713

I think we can close this as long as that other bug is closed, yup!

Status: NEW → RESOLVED
Closed: 11 months ago
Flags: needinfo?(nlapre)
Resolution: --- → FIXED
status-firefox114: --- → wontfix
status-firefox115: --- → wontfix
status-firefox116: --- → fixed
Target Milestone: --- → 116 Branch
You need to log in before you can comment on or make changes to this bug.