FA-31709 / Keyboard interactions / Member archive
Adjacent keyboard repeat batch coalescing: Repeat batch count uses timestamp arithmetic instead of event cardinality · case 04
The event trace violates the repeat count rule and produces incorrect keyboard state or command output.
Case contract
Events [kind,device,code,time,repeat]. Consecutive repeated down events for the same device/code coalesce into [device,code,first,last,count]; any nonrepeat or non-down event flushes the batch and is emitted as a raw event. A repeated down for a different token flushes and starts another. Return ordered entries tagged repeat or raw. 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 |
|---|---|---|---|
| repeat-coalescing scenario 2 | [[["repeat", "a", "A", 10, 12, 1]], [["repeat", "a", "A", 10, 12, 1]], [["repeat", "a", "A", 10, 12, 1]], [["repeat", "a", "A", 10, 12, 1]]] | [[["repeat", "a", "A", 10, 12, 2]], [["repeat", "a", "A", 10, 12, 2]], [["repeat", "a", "A", 10, 12, 2]], [["repeat", "a", "A", 10, 12, 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 ↗