A received down/up sequence proves the complete keyboard-to-browser path delivered that event.
IP-KEY-01 / KEY / CODE / LOCATION
Keyboard Repeat Behavior Test
Observe browser repeat events and timing while a single key remains held.
Held keys repeat too early, too late or irregularly.
This focused entry uses the shared Keyboard protocol. The measurement logic and Evidence version remain identical to the complete lab.
Remove the easiest false alarms first.
01
Match the visible layout, focus the test surface and close shortcut-heavy apps.
02
Press deliberate full chords; repeat the same chord before calling a key missing.
03
Test repeat and chatter with one key at a time so OS repeat is not confused with switch bounce.
Run one repeatable protocol.
- 01
Hold one printable key without releasing.
- 02
Wait for browser repeat events.
- 03
Compare initial delay and subsequent event spacing.
Evidence the result should expose.
DIRECT / INFERREDInitial delay
DIRECT / INFERREDMedian/P95 interval
DIRECT / INFERREDRepeat rate
DIRECT / INFERREDP95 jitter
Separate observed, review and inconclusive.
Repeat missing keys or rapid reactivations and compare the same chord in a plain text field or system tester.
Reserved shortcuts, OS repeat settings and browser focus can hide or reshape events without a keyboard fault.
Start with the likely path, then retest.
01
OS repeat settings
02
Application scheduling
03
Switch interruption