FA-38899 / Tree accessibility / Member archive

Paged tree children accessibility merge: Overlapping page duplicates or sorts sibling IDs · case 04

Overlapping page duplicates or sorts sibling IDs produces the wrong hierarchical widget state in a regression fixture.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

Only the expected cursor and branch revision admit a page. Repeated child IDs preserve their first position but update their record. An empty string is a valid next cursor. Logical count is authoritative when supplied; otherwise unknown. Focus on the load-more row moves to first newly inserted child, or parent if no continuation.

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
overlap page	`[["z", "a", "a", "y", "b", "y"], {"a": 3, "b": 8, "y": 5, "z": 1}, ["y", "b"], null, false, 12, "y", {"a": 3, "b": 5, "y": 6, "z": 1}]`	`[["z", "a", "y", "b"], {"a": 3, "b": 8, "y": 5, "z": 1}, ["y", "b"], null, false, 12, "y", {"a": 2, "b": 4, "y": 3, "z": 1}]`	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.