FA-31742 / Keyboard interactions / Member archive
Press-time remapping and logical key reference counts: A remap update does not affect future physical presses · case 02
The event trace violates the future map rule and produces incorrect keyboard state or command output.
Case contract
Events [kind,key,value]. Map replaces future press mapping; None disables output. Down captures current mapping once per physical key. Several physical keys mapping to one logical key share a reference count: emit logical down at 0->1 and up at 1->0. Release uses captured mapping even after remap. Reset emits sorted ups for all logical held keys and clears presses. Return events, captured physical map and logical counts. 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 |
|---|---|---|---|
| remap-release-ownership scenario 2 | [[[["down", "X"]], [["A", "X"]], [["X", 1]]], [[["down", "X"]], [["A", "X"]], [["X", 1]]]] | [[[["down", "Y"]], [["A", "Y"]], [["Y", 1]]], [[["down", "Y"]], [["A", "Y"]], [["Y", 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.
Sign in to the archive ↗