the pointer travelled to each control it pressed
Check id pointer-approach-per-target
What an ordinary browser yields
Movement leading to every control that was pressed. N/A on touch, pen, coarse-pointer devices and keyboard-only use (severity: warn).
What a detector infers
The gate asks for four separate acts in four separate places - three markers, a text field, a slider and a dropdown - and a pointer has to cross the distance to each one. This row measures the movement in the segment between one gate press and the next, so the question is not the weak "did the pointer ever move" that a driver satisfies by moving once, but "was every control approached". A press with zero movement behind it means the pointer was elsewhere, and then it was pressing here, with nothing in between - which is what dispatching a press at a computed coordinate produces and what an arm cannot do. It survives the native CDP click path: those clicks are genuinely isTrusted and pass every provenance row in the suite, and they still arrive with no travel. DEVICE HANDLING IS WHAT MAKES IT SCOREABLE. A finger has no approach - it arrives at the glass already touching - so a tap is a teleport by nature and scoring one would fail every phone. The row declines outright when any gate press came from touch or pen, and when the device reports a coarse pointer with no hover. A keyboard-only visitor presses with no pointer at all and never reaches the measured arm. What is left is a mouse or a trackpad, the only device for which the question means anything.
How to resolve it
Move the pointer to each target before pressing it - a sequence of mouseMoved dispatches along the way, not a single press at the destination. Nothing to fix for a person using a mouse or a trackpad: the travel is unavoidable.
Nearby checks in Automation surface
- keys were held down for a measurable moment
key-press-dwell-durationThe keyboard twin of the press-dwell row, and it is deliberately separate because the two fail independently - which SeleniumBase 4.51.5… - 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… - the pointer accelerated and slowed on its way to each control
pointer-approach-speed-profileA pointer moved by an arm leaves rest, accelerates, and brakes into its target, so the distance covered between consecutive samples rises… - 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… - pageXOffset/pageYOffset match their scrollX/scrollY aliases
scroll-alias-coherencewindow.pageXOffset is not a second scroll position, it is a legacy alias of window.scrollX — the specification defines them as the same… - a focused child frame implies its parent document is focused
document-focus-vs-realmdocument.hasFocus() is true when the document OR any of its descendants holds focus, which makes it hierarchical rather than local: a…
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 pointer-approach-per-target belongs to.