The pointer came to rest on a control before pressing it
At least one press follows the pointer's arrival by 15 ms or more. Notable only when every one of three or more presses was faster; N/A with fewer than three presses. A readout until calibrated (severity: info).
What a detector infers
A person brings the pointer onto a control and presses after it arrives: the hand has to stop, and then the finger has to act. This row measures that gap, the time from the pointer arriving within a few pixels of the press point to pointerdown.
A protocol-driven click sends the final move and the press together; measured, Playwright's click left 0.0 to 0.1 ms between arriving and pressing. pointer-arrival-to-press-interval already fails an interval of exactly 0 ms. This row looks just above zero, which needs calibration against real visitors that has not yet been done, so it is a readout.
It is also judged across every press rather than one: quick clickers and tap-to-click touchpads produce a fast press now and then, so it needs at least three presses and notes a visit only when every one of them came within 15 ms of the pointer arriving.
How to resolve it
Leave a pause between landing the pointer and pressing. A click sent as one burst — final move and press in the same instant — has no settle time at all.
Nearby checks in Input & behaviour
- An upper-case letter was typed with Shift or Caps Lock
shift-less-capitalsOn a physical keyboard, a capital letter is the letter key pressed with Shift held or Caps Lock on: the key event for 'H' arrives with code… - A mouse press landed inside the viewport it was delivered to
press-inside-viewportA physical mouse press lands wherever the pointer is. If the pointer is outside the page's viewport, the press goes to the browser's own… - A move only reports a button down after that button was pressed
buttons-without-pressMouseEvent.buttons on a move reports which buttons are held, and a button can only be held after it has been pressed. - The pointer never crossed a long distance in one report from rest
pointer-jump-from-restWhen a hand starts moving a mouse that has been still, the first reports cover a few pixels each as the movement builds up. - Pointer path curves the way a hand moves
pointer-path-linearityThe check captures the pointer path across the pad and measures two things about its geometry: the RMS perpendicular distance of every… - Pointer velocity and acceleration vary physically
pointer-kinematicsVelocity, acceleration reversals, direction changes, and timestamp quantisation catch constant-speed curved automation missed by linearity. - Pointer events arrive on hardware time
pointer-event-cadenceWhere the linearity check reads the path's shape, this one reads its clock. - Pointer samples arrive batched the way a hardware device delivers them
input-coalescing-vs-hardwareChrome delivers pointermove once per display frame and folds every hardware report that arrived in between into getCoalescedEvents()…
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 Input & behaviour 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 Input & behaviour — the family settle-before-press belongs to.