the element prototype chain matches its claimed Chromium major's
Check id element-surface-vs-baseline
What an ordinary browser yields
The element prototype chain exposes every member the population of real builds of your claimed Chromium major exposes.
What a detector infers
A for..in over the document element does not enumerate one object: it walks the whole prototype chain — HTMLElement, Element, Node, EventTarget — and returns every enumerable member on it, which in practice means every DOM property and every on* event handler the build was compiled with. Handlers arrive and leave on a different schedule from the platform globals, so this is a second clock, independent of the first. A build that matches the population on globals but not on the element chain has been assembled rather than shipped: some part of it comes from one version and some from another. As with the global-object row, only absence counts, the baseline needs 90% agreement across at least 25 captures of that major, and a major with no baseline yields N/A rather than a guess.
How to resolve it
The chain is compiled into Blink. If it is short of the claimed major's, the binary is older or trimmed — align the user agent with the engine that is actually running rather than the other way round.
Read in the wild by
FakeBrowser (collector)
Captures `for (const key in document.documentElement)` as `htmlElementVersion`, stored beside the window list — the field name is the tool's own admission of what the surface reveals: the version.
dumpHtmlElementVersion(), script/dumpDD.js
kkoooqq/fakebrowser script/dumpDD.js
Every attribution traces to a published artifact. See the sources and their limits.
Nearby checks in Automation surface
- no notifications-permission headless bug
permissions-notification-bugTwo independent APIs describe the same underlying notification permission: navigator.permissions.query({name:'notifications'}) returns a… - permissions.query is native (arity throw + stack shape)
permissions-query-stackThis probe calls navigator.permissions.query() with exactly zero arguments and inspects the error the native arity check produces. - timer handles are a real per-realm counter
timer-id-sequencingThe number setTimeout hands back is not a token, it is an index into the realm's own timer table — so it carries structure that a fabricated… - the global object carries every platform global its claimed Chromium major carries
window-globals-vs-baselineThe list of names on the global object is not written by the page — it is installed by the engine when it sets up a realm, from a table… - document.hidden agrees with document.visibilityState
document-visibility-coherencedocument.hidden and document.visibilityState are two views of one piece of state, and the specification defines the first in terms of the… - navigator.plugins is a real IDL collection, not a JavaScript object
plugins-idl-index-wraparoundA real navigator.plugins is a PluginArray — a C++-backed IDL collection — and its indexed getter runs the Web IDL unsigned-long conversion… - navigator.storage quota is the same in the window and a same-origin worker
storage-quota-worker-vs-mainnavigator.storage.estimate().quota describes one storage partition, and a same-origin worker shares that partition — a single QuotaManager… - performance.timeOrigin + performance.now() reconstructs Date.now()
clock-origin-coherenceA page has two clocks. performance.timeOrigin is the wall-clock moment its timeline began; performance.now() is the monotonic time elapsed…
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 element-surface-vs-baseline belongs to.