My apologies to the Bugzilla team for wasting their time holding my hand on this one. Would have honestly never noticed the little “HTML5” info icon to the left of the URL bar though without their help.
My apologies to the Bugzilla team for wasting their time holding my hand on this one. Would have honestly never noticed the little “HTML5” info icon to the left of the URL bar though without their help.
Surely this is a user experience that could be improved, no? Awesome feature but confusing solution.
The resist fingerprinting mode scrambles canvas read out to prevent sites from using it to create a fingerprint. Because of that, any site that needs to read the canvas back for legitimate purposes will also receive scrambled data. You get more privacy for the minor inconvenience of having to manually allow canvas usage for the sites that actually need it.
Yes I’m aware, but the user interface doesn’t make it easy to understand A) why the canvas looks scrambled, and B) how to permit it on a per-site basis.
The technical implementation is fine, it’s just the user workflow that needs fixed.
And very few sites actually need it.
Not really, because doing this will make you more fingerprintable (see my other comment). That’s why the default settings are striking a balance between making all users look similar and not breaking too many things (that would cause users to use user-specific overrides that make them more unique), and why
resistFingerprintingis inabout:configrather than a user-facing setting or enabled by default.Or use something like Chameleon and mess with
about:configwhich makes every unique fingerprint, different as your data is scrambled. Firefox still haswebRTCleakage, font fingerprinting, audio fingerprinting… That’s the reason why people use arkenfox’s user.js !On librewolf I just get a popup asking to allow canvas
A popup sounds like an annoyance you must deal with on every webpage. Not just the ones that use the canvas for useful things
Canvas is rarely on a web page or at least it rarely affects me