The field-trial state of this build is reported (XSLT warning banner)
Recorded only: whether an XSLT-rendered document received the deprecation banner. No answer is judged correct yet (severity: info).
What a detector infers
Chrome is deprecating XSLT, and a fresh Chrome 155 profile shows it: an XML document styled with XSLT is rendered with a red deprecation warning injected at the top. Measured on new profiles of Chrome 155 on Windows and Linux and of Edge 155.
It appears on profiles that have not yet received Chrome's field-trial configuration — the settings a browser downloads from its vendor after it first starts — and that is what makes it informative: it describes how this browser has been configured, not which version it says it is. Playwright's Chromium 149, which may simply predate the banner, and chrome-headless-shell show none. The row is a readout and is never scored, for two reasons stated plainly.
What an installed Chrome that has received its field-trial configuration shows has not been measured, so there is no established answer for most real visitors. And a genuinely new installation looks exactly like a fresh test profile on its first run. The value is recorded so that a baseline can be built; until then it carries no verdict.
How to resolve it
Nothing to fix. The banner reflects field-trial configuration and profile age, both of which vary legitimately; it is collected to learn what real installations show.
Nearby checks in Environment & locale
- MediaCapabilities powerEfficient agrees with WebCodecs prefer-hardware
power-efficient-vs-webcodecsMediaCapabilities.decodingInfo() reports whether decoding a format would be power-efficient, and WebCodecs' VideoDecoder.isConfigSupported()… - A playback AudioContext buffers more than an interactive one
playback-hint-buffers-moreAn AudioContext created with latencyHint 'playback' asks for a larger buffer than one created with 'interactive', and Chrome honours the… - AudioContext latencies are values Chrome's audio stack can produce
audio-latency-render-stateTwo AudioContext latencies are produced by the audio stack at particular moments, and their values are constrained in ways a constant is… - A granted geolocation fix carries a real accuracy
geolocation-has-accuracyEvery position a real location provider returns comes with an accuracy: the radius, in metres, within which the true position probably lies. - Intl timezone resolves
timezone-presentThis check reads Intl.DateTimeFormat().resolvedOptions().timeZone and records it alongside -new Date().getTimezoneOffset() and… - Timezone is not UTC
timezone-not-utcThe check resolves the Intl zone and fails only when it is exactly 'UTC' or 'Etc/UTC'. - IANA zone offset matches the JS clock offset (incl. across DST)
timezone-offset-coherenceThis is a two-source cross-check on the same fact. It takes the resolved IANA zone, formats the current instant through Intl.DateTimeFormat… - navigator.plugins is consistent with the PDF viewer
has-pluginsAn empty navigator.plugins is only meaningful when it contradicts something else, and this check is written to respect that.
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 Environment & locale 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 Environment & locale — the family xslt-banner-readout belongs to.