FAILURE MAP
← Case archive

FA-39744 / Tree accessibility / Member archive

Optimistic subtree move rollback ownership: Failed move rolls back a newer transaction · case 04

Failed move rolls back a newer transaction produces the wrong hierarchical widget state in a regression fixture.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

A failed optimistic move may roll back only while the current parent version and transaction ID match its write. Restore the subtree root at its original sibling position, restore descendant levels by inverse delta, preserve later unrelated selection, and recover focus only if the optimistic move owned it.

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 fixtureActualExpectedOutcome
new parent version["r", ["a", "b", "z"], ["x", "y"], {"b": 1, "c": 2, "outside": 0}, "c", ["c", "outside"], "rolled-back"]["q", ["a", "z"], ["x", "b", "y"], {"b": 6, "c": 7, "outside": 0}, "b", ["c", "outside"], "superseded"]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.

Sign in to the archive ↗