ungoogled-software/ungoogled-chromium

Spoof WebGPU info

Open

#3670 opened on Feb 25, 2026

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Python (18,674 stars) (771 forks)batch import
enhancementhelp wanted

Description

Description

The current "Spoof Webgl Info" option but for WebGPU.

Who's implementing?

  • I'm willing to implement this feature myself

The problem

Ungoogled Chromium has a patch which adds a "Spoof Webgl Info" option which replaces the UNMASKED RENDERER/VENDOR of WebGL with the string " " (an empty space). However, it is possible to get similar hardware information using the WebGPU API: await navigator.gpu.requestAdapter()

Possible solutions

Either integrate it into the existing option (since the intent is the same: hiding hardware information) or add a new option which redacts the vendor/device information like WebGL.

Alternatives

Adding an option to disable WebGPU entirely (like what we have with WebGL).

Extensions are not alternatives; they cannot inject code into web workers.

Additional context

No response

Contributor guide

Tech stack
cppjavascript
Domain
security
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C++Chromium internalsWebGPU API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by examining the existing 'Spoof WebGL Info' implementation in the ungoogled chromium patches. Look for where WebGL's UNMASKED RENDERER/VENDOR is replaced with a space. Then, identify the analogous WebGPU adapter properties (e.g., `navigator.gpu.requestAdapter()` and its `device`). Research how Chromium exposes this information and where to intercept it. Consider modifying the same patch files to also spoof WebGPU info, or create a new patch. The Chrome source code for GPU info is likely in `content/browser/gpu/` or similar. Review any open pull requests or comments for additional guidance.