WebGL renderer claims a hardware GPU but WebGPU exposes no real adapter (spoofed renderer)
br.webgpu_webgl_vs ·
What it catches
WebGPU (2024-25): a spoofed WebGL renderer with no WebGPU adapter may be exposed below the spoof. v0.74.5: category corrected coherence->ENVIRONMENT — the premise that a real hardware GPU drives BOTH is FALSE. WebGPU's hardware requirements (Vulkan 1.1+/D3D12/Metal, recent drivers) are a STRICT SUBSET of WebGL's, and Chrome blacklists many GPUs for WebGPU while WebGL still works — so a real Chrome user on an older/integrated GPU (pre-2015 Intel HD, older NVIDIA/AMD) or a blacklisted driver has navigator.gpu present but requestAdapter()=null while WebGL still reports the hardware renderer, tripping this. Confirmed: a webgpu_webgl_mismatch-only session scored bot. It must only CORROBORATE, never convict. The reliable companion br.webgpu_vendor_vs_webgl stays convicting: it fires only when a WebGPU adapter EXISTS and its GPU family disagrees with the WebGL renderer (the real GPU showing through a spoofed WebGL string). Renderer-spoofers are still caught by webgl_renderer_artifact / native_invariant_violated and the many other tells (full-stealth, native-spoof have 10+ each).
Signals it reads
browser.webgpu_webgl_mismatch
How it fires
present