This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Imprecise WebGL Renderer String

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by simi.11

simi.11
simi.11
more options

Hi, so I noticed that the "WebGL Renderer String", which Firefox returns upon request, seems to be quite imprecise in some cases.

My desktop machine has a Nvidia Geforce GTX 650 Ti built into it.

Google Chrome for example returns the exact and correct renderer string: "ANGLE (NVIDIA, NVIDIA GeForce GTX 650 Ti Direct3D11 vs_5_0 ps_5_0, D3D11-27.21.14.5671)"

Firefox instead seems to assign and return a more simple, generic renderer string, in my case: "ANGLE (NVIDIA, NVIDIA GeForce GTX 480 Direct3D11 vs_5_0 ps_5_0)"

This is of course a great feature in terms of privacy ("browser-fingerprinting"). Nonetheless I didn't find any information about the rules which are applied, before such a more generic renderer string is being returned by Firefox. It would be cool if someone could share an insight with me!

Best regards

Hi, so I noticed that the "WebGL Renderer String", which Firefox returns upon request, seems to be quite imprecise in some cases. My desktop machine has a Nvidia Geforce GTX 650 Ti built into it. Google Chrome for example returns the exact and correct renderer string: "ANGLE (NVIDIA, NVIDIA GeForce GTX 650 Ti Direct3D11 vs_5_0 ps_5_0, D3D11-27.21.14.5671)" Firefox instead seems to assign and return a more simple, generic renderer string, in my case: "ANGLE (NVIDIA, NVIDIA GeForce GTX 480 Direct3D11 vs_5_0 ps_5_0)" This is of course a great feature in terms of privacy ("browser-fingerprinting"). Nonetheless I didn't find any information about the rules which are applied, before such a more generic renderer string is being returned by Firefox. It would be cool if someone could share an insight with me! Best regards

Chosen solution

Perhaps it's due to bug 1715690 and 1722113.

Can you see the real string in about:support?

Try to set webgl.enable-renderer-query = false and webgl.sanitize-unmasked-renderer = true prefs in about:config.

Read this answer in context 👍 1

All Replies (2)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

Chosen Solution

Perhaps it's due to bug 1715690 and 1722113.

Can you see the real string in about:support?

Try to set webgl.enable-renderer-query = false and webgl.sanitize-unmasked-renderer = true prefs in about:config.

simi.11
simi.11 Question owner
more options

TyDraniu said
Perhaps it's due to bug 1715690 and 1722113. Can you see the real string in about:support? Try to set webgl.enable-renderer-query = false and webgl.sanitize-unmasked-renderer = true prefs in about:config.

These two links helped me a lot. Thank you very much TyDraniu!

In about:support I can find the real string, so it got bucketed which of course is a good thing.

I tried to change the config settings but that did not reveal the real string (which is fine)

Modified by simi.11