dragging the slider moved it through the values it crossed
Check id slider-drag-value-progression
What an ordinary browser yields
A dragged slider passing through several intermediate values. N/A when it was clicked, stepped with the keyboard, or not dragged at all (severity: warn).
What a detector infers
A 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 of values rather than a single act. A thumb dragged across a track reports every value it passes through; a thumb placed at the destination reports one. Measured on Chrome 150: a hand dragging the thumb produced 27 distinct intermediate values across 31 held moves, while every automated route produced one or none - click_with_offset one, set_value zero, and SeleniumBase 4.51.5's mouse_drag one. The first design of this row was 'few input events means automation' and it was wrong, which is worth recording: clicking the track jumps the slider straight to a value and fires exactly one input event, and that is an ordinary thing for a person to do. So the row asserts nothing at all unless a drag was actually observed - a press on the slider followed by at least one move with the button still held - and declines for a track click or an arrow-key step. Note what it deliberately does NOT claim: SeleniumBase's mouse_drag also lands on the wrong value entirely (50 instead of 70, because its single intermediate move reports buttons 0 so the slider never tracks it), but that is not scored here. With no held move it is not a drag, and pointer-buttons-during-drag already covers it. What this row uniquely catches is the driver that carries the button mask correctly and still teleports the thumb in one jump.
How to resolve it
Move the pointer across the track in steps while the button is held, rather than pressing at the start and jumping to the end. The slider reports a value for every position it actually passes through, so a drag that skips the middle is visible in what it never reported.
Nearby checks in Automation surface
- 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… - 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… - 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… - 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 slider-drag-value-progression belongs to.