FA-31569 / Keyboard interactions / Member archive

Keyboard macro recording timebase: Stopping leaves recording enabled or a stale pause flag · case 04

The event trace violates the stop recording rule and produces incorrect keyboard state or command output.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

Events [kind,key,time,injected]. Start resets capture and origin; physical down/up record relative active time; injected events are ignored. Pause freezes recording and resume excludes paused duration. Stop ends recording; clear erases recording. Return [kind,key,offset] records, recording flag, paused flag and excluded time. Ordered times and paired pause/resume. 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
macro-record scenario 7	`[[[["down", "A", 6]], true, false, 0], [[["down", "A", 6]], true, false, 0], [[["down", "A", 6]], true, false, 0], [[["down", "A", 6]], true, false, 0]]`	`[[[], false, false, 0], [[], false, false, 0], [[], false, false, 0], [[], false, false, 0]]`	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.