Web Share is present or absent as the claimed platform's Chrome ships it
navigator.share exists under a Windows or macOS claim and not under a desktop Linux claim. N/A on mobile, on Brave, outside secure contexts and on non-Chromium engines (severity: warn).
What a detector infers
navigator.share is present or absent depending on the platform the Chrome binary was built for. Chrome switches Web Share on in its renderer only for Windows, macOS, ChromeOS and Android — the source comment says it is kept away from WebView and Linux — so desktop Linux Chrome never has it, and every other desktop Chrome does. Measured that way: present on Chrome and Edge on Windows, absent on genuine Linux Chrome.
That makes the API a one-call check on the claimed platform, and both directions fail in practice: Linux Chrome claiming Windows has no navigator.share, and Windows Chrome claiming Linux has one. chrome-headless-shell never has it, even on Windows, because it does not use Chrome's renderer setup, so a headless shell under a Windows user agent fails too.
Web Share requires a secure context, so the row is N/A on plain http, and only desktop claims are asserted; Brave makes its own choice about Web Share and is N/A. Linux users can force it on with --enable-blink-features=WebShare, which is rare enough to state rather than exempt. It is the sibling of bluetooth-availability-vs-platform: an API whose presence is a property of the build.
How to resolve it
Present the platform the browser was built for. Whether the API exists is decided when Chrome is built and started, so defining or deleting navigator.share from script leaves a property without the native binding behind it.
Nearby checks in Capability surfaces
- C:/ parses the way the claimed OS's Chromium parses it
url-drive-letter-vs-osChromium's URL library contains a Windows-only rule: a string that begins with a drive letter, such as 'C:/x', is treated as a file path and… - The system colour palette belongs to the claimed OS
system-colors-vs-osWindows and Linux Chrome resolve the CSS system colours and their built-in form-control styles differently, and some of the differences are… - hrefTranslate is present under the Google Chrome brand
href-translate-vs-brandHTMLAnchorElement.prototype.hrefTranslate is a runtime-enabled feature that Chrome only switches on when its translation service is… - The device-API family is present or absent as a unit
device-api-family-coherenceWeb Bluetooth, WebUSB, WebSerial and WebHID are one family on Chromium desktop - the same secure-context gating, the same desktop platforms… - A build claiming Chrome carries the Privacy Sandbox surface Chrome ships
privacy-sandbox-vs-chrome-claimTopics, Protected Audience, Shared Storage and Fenced Frames all shipped to Chrome stable in 115 and are present by default on desktop. - Firefox resistFingerprinting announces itself when enabled
firefox-resist-fingerprinting-identifiableFirefox's privacy.resistFingerprinting substitutes CONSTANTS rather than randomness, and a constant is itself a fingerprint. - The CSS feature surface is identical in a fresh realm
css-surface-vs-realmWhich CSS properties, values and selectors an engine understands is decided when the browser is compiled. - Device-level media features are identical in a fresh realm
media-surface-vs-realmMedia features are answered by the layout engine rather than by the JavaScript properties that describe the same machine, which is what…
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 Capability surfaces 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 Capability surfaces — the family web-share-vs-os belongs to.