FA-38688 / Tree accessibility / Member archive

Accessible subtree reparent transaction: Reparent reveal option ignores expansion intent · case 03

Reparent reveal option ignores expansion intent produces the wrong hierarchical widget state in a regression fixture.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

The closure contains a moved subtree and the source and destination are distinct parents. Reject drops into that closure or a read-only destination. Accepted moves replace the root parent, shift every descendant level by the parent-depth delta, invalidate sibling metadata, retain ID-based selection and focus, and increment only affected parent versions.

Why this case matters

Offline executable model of a hierarchical accessibility interaction; inputs are bounded and valid as stipulated. No browser, assistive technology, or normative ARIA conformance is claimed.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
no reveal	`["q", {"b": 5, "c": 6, "outside": 0, "q": 4, "r": 0}, ["a", "z"], ["x", "b", "y"], ["q", "r"], {"outside": 8, "q": 8, "r": 4}, "c", ["c", "a"], ["q", "r"]]`	`["q", {"b": 5, "c": 6, "outside": 0, "q": 4, "r": 0}, ["a", "z"], ["x", "b", "y"], ["q", "r"], {"outside": 8, "q": 8, "r": 4}, "c", ["c", "a"], ["r"]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.