FA-31169 / Keyboard interactions / Member archive
Per-key double tap recognizer: A valid first release at timestamp zero is mistaken for missing history · case 04
The event trace violates the zero timestamp rule and produces incorrect keyboard state or command output.
Case contract
Case [window,events] with nondecreasing timestamps and events [kind,key,time]. Down repeats do not count. A matched up produces tap and may complete a double if the prior release of the same key is within the inclusive window. Completing a double consumes that prior release. Cancel clears that key, blur clears all state. Return doubles [key,time], held keys and remembered release times. 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 |
|---|---|---|---|
| double-tap scenario 3 | [[[], [], [["A", 4]], 2], [[], [], [["A", 4]], 2], [[], [], [["A", 4]], 2], [[], [], [["A", 4]], 2]] | [[[["A", 4]], [], [], 2], [[["A", 4]], [], [], 2], [[["A", 4]], [], [], 2], [[["A", 4]], [], [], 2]] | 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 ↗