FA-39734 / Tree accessibility / Member archive
Hierarchical branch command lock: Rejected or read-only command starts a subtree lock · case 04
Rejected or read-only command starts a subtree lock produces the wrong hierarchical widget state in a regression fixture.
Case contract
A pending subtree mutation locks that branch and descendants, but does not lock siblings. Read-only inspection remains available. New commands use nearest locking ancestor for reason attribution; completed operation tokens release only their owned locks and never a replacement lock.
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 fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| inspection | [true, null, {"b": "B", "c": "N4", "q": "Q", "r": "R"}, ["r", "b", "c", "q", "s"]] | [true, null, {"b": "B", "q": "Q", "r": "R"}, ["r", "b", "c", "q", "s"]] | 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 ↗