Chromium UA but the WebGL renderer is not ANGLE-wrapped — renderer spoof
br.webgl_not_angle ·
What it catches
Modern DESKTOP Chrome reports 'ANGLE (vendor, renderer, backend)'; a bare GPU string under a Chromium UA can be a renderer spoof. v0.74.6: category corrected coherence->ENVIRONMENT — 'always ANGLE' is FALSE for legacy/non-ANGLE Chrome configs (Linux Chrome with native GL reports a bare 'Mesa …' string; --use-gl=desktop / older builds / some Electron-Chromium do too). The rule's own prior note already flagged this residual FP, and the second source confirms it: webgl_not_angle was ~2.3% FP on browserforge (all legit non-ANGLE fingerprints) while catching ZERO evaders in the fleet — pure FP, no demonstrated detection value. So it must only CORROBORATE, never convict. Naive bare-renderer spoofs are still caught by br.webgl_renderer_artifact (placeholder/'or similar' strings) and the cross-layer GPU tells; a bare string now corroborates rather than convicting a real Linux Chrome.
Signals it reads
browser.webgl_not_angle
How it fires
present