Disable WebGPU when RFP is enabled
Categories
(Core :: Graphics: WebGPU, enhancement)
Tracking
()
People
(Reporter: tjr, Unassigned)
References
(Blocks 1 open bug)
Details
Until we understand the fingerprinting implications of WebGPU and if/how we can mitigate it - we should disable it.
|
Reporter | |
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
Surely this is Tor Browser's to flip/enforce dom.webgpu.enabled as false, not main stream Firefox, for now? I mean we don't disable webaudio or webGL APIs, so why should webGPU be any different?
|
|
||
Comment 2•3 years ago
|
||
PS: There are a raft of prefs/UI we could/should enforce to harden RFP against user/pref fiddling, and I do get that webGL's case is different as it is integrated with the slider (and NoScript) in Tor Browser. So I'm torn - I'm all for tightening, but is this one of those cases?
|
|
Reporter | |
Comment 3•3 years ago
|
||
That's a good point; it probably is up to Tor Browser. I'm going to leave this open for now until I can think about it more, double check a few things, and close it.
|
|
Reporter | |
Updated•1 year ago
|
Description
•