FA-31099 / Keyboard interactions / Member archive
Tap versus hold command arbitration: A fresh press is marked already dispatched or anchored to time zero · case 04
The event trace violates the initial held rule and produces incorrect keyboard state or command output.
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 fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| hold-threshold scenario 1 | [[[], [["A", 10, true]]], [[], [["A", 10, true]]], [[], [["A", 10, true]]], [[], [["A", 10, true]]]] | [[[], [["A", 10, false]]], [[], [["A", 10, false]]], [[], [["A", 10, false]]], [[], [["A", 10, false]]]] | 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 ↗