FAILURE MAP
← Case archive

FA-31758 / Keyboard interactions / Member archive

Press-time remapping and logical key reference counts: Physical press ownership stores event payload instead of the resolved logical target · case 03

The event trace violates the captured target rule and produces incorrect keyboard state or command output.

Member previewVariant 3 · 3 implementations · 9 checks per implementation

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 fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
remap-release-ownership scenario 2[[[["down", "Y"]], [["A", "A"]], [["Y", 1]]], [[["down", "Y"]], [["A", "A"]], [["Y", 1]]], [[["down", "Y"]], [["A", "A"]], [["Y", 1]]]][[[["down", "Y"]], [["A", "Y"]], [["Y", 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 ↗