Possibility to disable WebGL

[Artem13327]

Platforms

Android

Description

Sometimes you just need to turn it off and that's it.

[TEMP-ad]

You can use the adblocker for that.

Example:

webgl.org,webglsamples.org##+js(prevent-canvas, webgl)

Also, you can still enable the brave://flags/#brave-show-strict-fingerprinting-mode and then you can set websites to strict and break webgl, which is the reason why they improved it, because webgl used to be broken on it and people would complain, but you enable it, set some sites to strict fingerprinting and done, no webgl.

Adblocker is the easiest way and the better one, no reason for anyone to implement anything because I don't know why would anyone needs to turn it off, just don't go to a webgl website and if it is needed it is to render some 3D that should be needed, so yeah.

There is also the commandline like on Desktop, you do it through the Developer Options, the QA Code is qaonly and you do the same you would do on desktop with the --disable-webgl, but that's and all or nothing change, so I doubt you want that.

[Artem13327]

just don't go to a webgl website

I almost never go there on purpose, I am concerned that in some cases WebGL can provide additional data about the user

[TEMP-ad]

Well, Brave already has fingerprinting support to cover this, that was the problem with the strict fingerprinting support, it just broke the thing, so you might want to enable that for your case.

But you can see here https://dev-pages.bravesoftware.com/fingerprinting/farbling.html and/or https://dev-pages.brave.software/fingerprinting/farbling.html (for the 'other site') how Brave will randomize the values, and Brave now randomizes them per site, and per window, and per profile, so opening the same site on different profiles with randomize the values (at least on Nightly, because I only use Nightly, so if it doesn't happen on your side because I don't know how far behind is Stable, don't worry, it is coming), so 'they' if ever, will think you are a different person based on the fingerprinting values.

Anyway you can see which stuff is being farbled and understand how Brave's fingerprinting protection works.

The problem with the strict mode, was that random people enabled it and then complained about webgl sites not working, but if you test it it will farble more values like WebGL Vendor and Render and it will work with new fingerprinting mode and the exceptions lists and all and all that, so you are not losing anything, just adding more that will break webgl. the only thing that I notice is that strict fingerprinting values for webgl will not get farbled per window, profile or site, https://dev-pages.bravesoftware.com/fingerprinting/strict-mode.html but they will be different from your original one, so I guess that's what you want.

Brave doesn't allow Global Scriptlet rules, so you can't run that rule to block Webgl in all websites sadly. but anyway I guess strict mode, knowing it will break all sites with webgl and you can just set it to standard when needed is better. Of course I think it is a little paranoia extreme to worry about it, but you do you, and if Brave still allows to enable it then go for it.