FAILURE MAP
← Case archive

FA-32279 / Keyboard interactions / Member archive

Deferred short shortcut versus longer key sequence: Mismatch retry loses the current key or retries the already failed prefix · case 04

The event trace violates the retry current rule and produces incorrect keyboard state or command output.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

Case [bindings,timeout,events]. Binding [nonempty_key_sequence,action] has unique sequence. Events [kind,key,time]. Down extends prefix. Exact match with longer candidates is delayed until deadline; exact unambiguous match dispatches immediately. Tick or next event at deadline emits pending exact match and clears prefix. Mismatch dispatches pending match then retries only current key as fresh prefix. Cancel drops pending without dispatch. Return [action,time] dispatches,buffer,pending action,deadline. 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 fixtureActualExpectedOutcome
ambiguous-shortcut-prefix scenario 4[[[["short", 12]], [], null, null], [[["short", 12]], [], null, null], [[["short", 12]], [], null, null], [[["short", 12]], [], null, null]][[[["short", 12], ["other", 12]], [], null, null], [[["short", 12], ["other", 12]], [], null, null], [[["short", 12], ["other", 12]], [], null, null], [[["short", 12], ["other", 12]], [], null, null]]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 ↗