FA-38977 / Tree accessibility / Member archive

Tree expansion undo journal: Undo focus visibility ignores forced or closed ancestry · case 02

Undo focus visibility ignores forced or closed ancestry produces the wrong hierarchical widget state in a regression fixture.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Undo restores the prior expansion set only for surviving branches. Non-undoable loading and filter expansions remain separate. Journal entries belong to a tree generation; stale generations are discarded. Focus restored from journal must be visible under restored expansion.

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
undo latest	`[["a", "r"], ["a", "q", "r"], [{"after": ["a"], "before": ["r"], "focus": "r", "generation": 2}], [{"old": true}, {"after": ["r"], "before": ["r", "a", "gone"], "focus": "b", "generation": 2}], ["r", "a", "b", "q"], "b"]`	`[["a", "r"], ["a", "q", "r"], [{"after": ["a"], "before": ["r"], "focus": "r", "generation": 2}], [{"old": true}, {"after": ["r"], "before": ["r", "a", "gone"], "focus": "b", "generation": 2}], ["r", "a", "b", "q", "s"], "b"]`	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.