WebGL vendor, renderer, context attributes, extensions, parameters and
shader precisions, for WebGL1 and WebGL2, now come from fpgen's recorded
Firefox devices instead of webgl_data.db, which is deleted with the
camoufox/webgl/ package.
camoufox/webgl.py:
- webgl_for_gpu() traces `webgl` given Firefox, the OS and the GPU, then
`webgl2` given the chosen `webgl` too, and draws each with one seeded
random.Random. The GPU and the webgl value are pinned by their fpgen
lookup index: a dict condition is flattened into leaves that overwrite
each other, so only the renderer applied and Linux "Mesa" and "AMD"
Radeon HD 3200 devices came back mixed.
- sample_webgl_for_screen() draws the GPU of a generated identity from
fpgen's per-OS weights, filtering out software rasterisers, GPUs the OS
cannot report, discrete GPUs behind a netbook screen and the
resistFingerprinting "Mozilla" mask before the weighted choice, so there
is no rejection loop. An empty pool raises.
- The draft/host-dependent extension filter moves over unchanged.
A preset's GPU and a caller's webgl_config pair are looked up as given;
a pair fpgen has never seen from Firefox on that OS raises instead of
falling back to another GPU. generate_context_fingerprint no longer
falls back to the host GPU when the draw fails.
For 10 of the 15 (GPU, OS) pairs the two sources share, one of fpgen's
records converts to exactly the database row on every value the browser
reads. The other five rows (Linux R9 200 and Radeon HD 3200, macOS
Intel HD, and two software rasterisers) are devices fpgen does not carry;
those GPUs now present fpgen's recorded devices instead. The Linux
GTX 980 row is kept as a test fixture.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
