FA-31119 / Keyboard interactions / Member archive

Tap versus hold command arbitration: The pending state does not record that a hold has already dispatched · case 04

The event trace violates the mark emitted rule and produces incorrect keyboard state or command output.

Member previewVariant 4 · 3 implementations · 9 checks per implementation

Case contract

Case [threshold,events]. Events [kind,key,time]. Down arms an unarmed key. Tick emits hold once when age >= threshold. Up before threshold emits tap, at or after threshold emits hold if not yet emitted. Cancel removes just one key silently. Return output and pending [key,start,held] entries. 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
hold-threshold scenario 4	`[[[["hold", "A"], ["hold", "A"], ["hold", "A"]], []], [[["hold", "A"], ["hold", "A"], ["hold", "A"]], []], [[["hold", "A"], ["hold", "A"], ["hold", "A"]], []], [[["hold", "A"], ["hold", "A"], ["hold", "A"]], []]]`	`[[[["hold", "A"]], []], [[["hold", "A"]], []], [[["hold", "A"]], []], [[["hold", "A"]], []]]`	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.