the dropdown fired input before change
input before change on every selection, in the order the spec defines. N/A when no change was fired (severity: warn).
What a detector infers
HTML's "send select update notifications" steps fire input and THEN change when a selection is committed, so the pair is what the algorithm produces and a lone change is what a hand-dispatched event looks like.
Measured on Chrome 150 against SeleniumBase: a single change event with no input before it, from a helper that dispatches one constructed Event on the option - on 4.51.3 from every select helper, and on 4.51.5 still from select_option_by_value and select_option_by_index, which were not migrated when select_option_by_text was.
Kept separate from the trust row above because the two fail independently - a driver dispatching from a privileged context could produce a trusted change that still arrives alone, and a driver that fired both events could still fire them untrusted. Scoring the ordering and the provenance as one row would let either fix hide the other.
How to resolve it
If the selection must be synthesised, dispatch input and then change, in that order, on the <select> itself rather than on the option. Driving the element through real input avoids the question, because the engine emits both.
Nearby checks in Automation surface
- the clicks this page received were real clicks
interaction-click-trustEvent.isTrusted is set by the engine when it dispatches an event it generated itself, and it cannot be set from script - a constructed… - every keypress had a keydown behind it
interaction-keypress-without-keydownThe UI Events spec generates keypress as the DEFAULT ACTION of a keydown - it is not an independent event, it is what a keydown does when it… - key events named the key they carried
interaction-key-identity-populatedA keypress the engine generates names the character it is delivering in .key. - the dropdown change came from the browser, not from a script
interaction-select-change-trustThe same isTrusted argument as the click row, on the surface where the shortcut is most common. - the text in the field arrived through events
interaction-value-without-eventsText cannot appear in a field without the engine having put it there, and every route the engine offers announces itself with an input event… - the pointer moved before it clicked
pointer-movement-precedes-clickA mouse reaches a target by crossing the document, and every position it crosses is an event. - 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.
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 interaction-select-input-precedes-change belongs to.