Signals · display · counted, not scored by the rubric
Usable screen area
screen.availWidth by screen.availHeight: the screen minus the taskbar, the dock or the menu bar.
Rubric 1.0.0 does not print a prior for this value. The population still compares it, so the box beside this text counts how many of the devices these sites have read share yours.
How a page reads it
Two numbers read straight from the screen object. They describe the desktop, not the browser window, so resizing the window does not change them.
Why it splits browsers apart
Two laptops with the same screen often differ here: a dock on the left, a taller taskbar, a menu bar on a second monitor. That makes this value rarer than the screen size it comes from.
What moves it
Moving or resizing the taskbar or dock, changing display scaling, or plugging in another monitor.
What moving it costs
A spoofed screen size with a usable area that does not fit inside it, or one that matches no real taskbar layout, is a contradiction a page can compute in one line.
How the count is made
Your value is compared with the latest reading of every device the eight sites read in the last 365 days, this browser's own rows left out. The share is (devices sharing it + 1) ÷ (population + 1), and the bits are −log₂ of that. Why the counts sit beside the priors and are never added to them.
Questions about usable screen area
- Why is the usable area different from my screen size?
- The operating system keeps part of the screen for the taskbar, the dock or the menu bar. The browser reports the rest, and that remainder depends on how your desktop is arranged.
- Does it leave the device key?
- Yes. It moves with desktop settings and second monitors, so the key uses the full screen size instead.
In the same group
Next
Script memory limit: performance.memory.jsHeapSizeLimit: the most memory the JavaScript engine will use for one page, in bytes.
Where the pens move
A value patched in the page is a patched value. Set in the engine, it is just a value.
Engine level, not JS level. Donut Browser spoofs through CDP injection in its Wayfern Chromium fork, so the value a page reads is the value the engine reports — there is no patched accessor to catch.
It refuses to contradict itself. A profile whose proxy exit geography, time zone or language disagrees with its fingerprint does not launch. That is a pre-launch gate in the app, not advice in a manual.
Open, and quiet. AGPL-3.0, desktop app and sync server both in the repository, and no analytics SDK anywhere in the source. macOS, Windows, Linux.