Exposing WEBGL_debug_renderer_info extension to Web content will allow sites to detect bad GPUs and temporarily workaround GPU problems. If we can workaround the GPU problem in Gecko, then we can stop exposing that GPU's WEBGL_debug_renderer_info extension to reduce user fingerprinting.

This may very well be a whitelist approach instead - don't expose the "good" ones. That way, if the new drivers are bad, they would give us the info before we discover and confirm they are bad.

My understanding is that we're categorically against exposing the renderer string to web content. In part because of fingerprinting, in part because it's a part privacy issue (your GPU tells a lot about you to marketers). But also we're afraid that this information wont be used properly most of the time and lead to web compatibility issues. I don't know what the author would do with the renderer information. Either we are confident in the renderer or we're not and the renderer is not much use then. I think this is a WONTFIX but I'm just repeating what I've heard. I'll let Jeff make the official call.

(In reply to Benoit Girard (:BenWa) from comment #2) > My understanding is that we're categorically against exposing the renderer > string to web content... There is a dev-platform discussion on this topic.

Bug 1336645 will expose WEBGL_debug_renderer_info for all GPUs, not just blocklisted ones.