Closed Luke0094 closed 10 months ago
Which of the 2 fingerprint blocking setting values have you set it to? I don't believe this has ever worked with Brave's "Aggressively block fingerprinting" turned on because then the browser blocks features of WebGL that the extension needs.
Was set on aggressive (sorry, I had another language set so my translation was based on it). It doesn't have much sense to keep it to "normal" since basically all your spec are in plain sight in this way. Any fix?
Any fix?
Brave's "Aggressively block fingerprinting" blocks features of WebGL that the extension needs: https://github.com/brave/brave-browser/issues/9188
It might also be good to know that Brave is considering to remove aggressive fingerprinting mode: https://github.com/brave/brave-browser/issues/31229
Thank you for the reply, actually I've just found from your screen that you can change the behavior for a specific website while still maintaining the agressive rule active in general.
Bug description
As title say if you enable that option WebGL crash, to my knowledge it wasn't before (unsure)
Steps to reproduce the behavior
Browser
Chrome
Operating system
Windows
Extension version
2.37.29
The bug still happens in these conditions
Additional context and/or screenshots
No response