keys were held down for a measurable moment
Check id key-press-dwell-duration
What an ordinary browser yields
A shortest key hold of tens of milliseconds. N/A when IME composition was used, when no keydown/keyup pair was measurable (paste, autofill and dictation produce none), or on a coarsened clock (severity: warn).
What a detector infers
The keyboard twin of the press-dwell row, and it is deliberately separate because the two fail independently - which SeleniumBase 4.51.5 demonstrates precisely. That release FIXED the key sequence: it now emits rawKeyDown, char and keyUp with key, code and the virtual key codes populated, so every structural keyboard row on this page passes. Measured over a 49-character phrase on Chrome 150, the timing did not change: keydown-to-keyup was 1.0ms under send_keys and 1.4ms under press_keys - which is its explicitly human-paced mode - against 96ms for a hand-driven control. press_keys spaces the CHARACTERS convincingly, roughly 50ms apart, and still releases each key 1.4ms after pressing it. That is the whole point of measuring the hold separately from the rhythm: a driver can fix the gaps between keys, and fix the event sequence, and still be releasing keys faster than any finger. Auto-repeat keydowns are excluded from pairing, because a held key emits many keydowns and one keyup and pairing across that would measure the wrong interval entirely.
How to resolve it
Dispatch keyUp on a later tick than rawKeyDown rather than immediately after it. Typing helpers that space out characters commonly still release each key instantly, which fixes the rhythm between keys while leaving the hold itself impossible.
Nearby checks in Automation surface
- arriving over a control and pressing it were separate moments
pointer-arrival-to-press-intervalpointerover fires when the pointer arrives over an element; pointerdown fires when the button goes down. - a held mouse button reported some pressure
pointer-pressure-on-pressPointerEvent.pressure is not a range to model, it is a constant to check. - the document was scrolled by something that can scroll it
scroll-input-attributionA document moves for a reason: a wheel notch, a scroll key, a finger, a scrollbar drag - or a script. - the mouse button was held down for a measurable moment
pointer-press-dwell-durationA mouse button is a mechanical switch. Its contacts bounce for several milliseconds before the signal settles, and the hand above it is far… - movement while a button was down reported the button as down
pointer-buttons-during-dragMouseEvent.buttons is a bitfield of which buttons are currently held, derived by the browser from the physical button state rather than from… - dragging the slider moved it through the values it crossed
slider-drag-value-progressionA range slider is the only common control that has to be DRAGGED to be used as intended, which makes it the only one that produces a stream… - clicks landed on different points, not the same one repeatedly
pointer-landing-dispersionAiming is imprecise. A hand lands somewhere inside a control and the spread shows up within two or three clicks; a driver resolves the… - no automation pointer-flash artifact is present
pointer-flash-keyframe-artifactThe only row on this page that works by recognising a specific string, which needs justifying because a name table is exactly what this…
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Automation surface checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Automation surface — the family key-press-dwell-duration belongs to.