FA-31377 / Keyboard interactions / Member archive

Sticky modifier latch lifecycle: Character dispatch consumes locked latches or preserves one-shot modifiers · case 02

The event trace violates the once consumption rule and produces incorrect keyboard state or command output.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

Events [kind,key]. Tap of modifier cycles absent -> once -> locked -> absent. Modifier down/up sets physical state independently. Character emits [key,sorted effective modifiers] then consumes all once latches but preserves locked and physical modifiers. Cancel clears latches only; blur clears both. Return emitted events, latches and physical state. 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 fixture	Actual	Expected	Outcome
sticky-modifiers scenario 1	`[[[["A", ["Shift"]], ["B", ["Shift"]]], [["Shift", 1]], []], [[["A", ["Shift"]], ["B", ["Shift"]]], [["Shift", 1]], []]]`	`[[[["A", ["Shift"]], ["B", []]], [], []], [[["A", ["Shift"]], ["B", []]], [], []]]`	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.