The pointer never crossed a long distance in one report from rest
After at least 50 ms at rest, the next pointer report moves less than 100 pixels. A readout until calibrated against real visitors (severity: info).
What a detector infers
When a hand starts moving a mouse that has been still, the first reports cover a few pixels each as the movement builds up. A single DevTools-protocol mouseMoved event, by contrast, places the pointer at its destination in one report, however far away that is. This row looks for a pointer that was at rest for at least 50 ms and then crossed 100 pixels or more in its very next report; the pointer entering the page, or coming back to it after leaving, does not count.
Measured: Playwright's mouse.move produced single-report jumps of 943, 348 and 319 pixels, and a raw protocol event 361 pixels. What real visitors look like has not been measured — there is no human pointer data in this run — so the row is a readout until it can be calibrated.
There are honest ways to jump, too: eye-tracking and voice-controlled cursors, pen tablets in absolute mode, where the pointer goes wherever the pen touches down, and remote-desktop connections that drop intermediate reports. It complements pointer-movement-precedes-click and the approach rows, which ask whether a path existed; this one looks at its first step.
How to resolve it
Move the pointer along a path in many small reports — Playwright's mouse.move takes a steps option — rather than placing it at the target in one event.
Nearby checks in Input & behaviour
- Every raw pointer update carries at least its own sample
rawupdate-carries-its-samplepointerrawupdate fires for each pointer report as it arrives, without waiting for the next frame, and Chrome builds each one from a real… - 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 came to rest on a control before pressing it
settle-before-pressA person brings the pointer onto a control and presses after it arrives: the hand has to stop, and then the finger has to act. - 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.
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 pointer-jump-from-rest belongs to.