FA-31939 / Keyboard interactions / Member archive
Release-completed dot chord keyboard: Separator is represented as a padding dot or omitted instead of an explicit empty chord · case 04
The event trace violates the separator empty rule and produces incorrect keyboard state or command output.
Case contract
Events [kind,dot]. Dot values 1..8. Down adds a dot to held and accumulated chord; repeated down does not add another dot. Up releases a held dot and commits sorted accumulated dots only when the final held dot is released. Cancel clears held/chord without output; separator commits pending chord then emits empty dot list and resets. Return committed dot lists, held and accumulated sets. Inputs are finite ordered event traces; return the stated deterministic state. Batch entries are independent. N varies the number of independent input transactions.
Why this case matters
Controlled keyboard event processing model for debugging application event logic.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| braille-chord scenario 8 | [[[[1, 2], [0]], [], [], 0], [[[1, 2], [0]], [], [], 0], [[[1, 2], [0]], [], [], 0], [[[1, 2], [0]], [], [], 0]] | [[[[1, 2], []], [], [], 0], [[[1, 2], []], [], [], 0], [[[1, 2], []], [], [], 0], [[[1, 2], []], [], [], 0]] | 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 ↗