Locked sticky issue for tracking privacy.resistFingerprinting
Last updated: see changelog at foot (regularly cleaned out)
:small_red_triangle_down: FF41
:small_red_triangle_down: FF50
:small_red_triangle_down: FF55
:small_red_triangle_down: FF56
:small_red_triangle_down: FF57
:small_red_triangle_down: FF58
privacy.resistFingerprinting.autoDeclineNoUserInputCanvasPrompts )manifest.url and on that page, right click >View Page Info>Permissions and set a canvas exceptionprivacy.resistFingerprinting:small_red_triangle_down: FF59
privacy.spoof_english (pref is used internally AFAICT, we should not meddle with it):small_red_triangle_down: FF60
2011):small_red_triangle_down: FF62
:small_red_triangle_down: FF63
no-preference with prefers-reduced-motion:small_red_triangle_down: FF64
:small_red_triangle_down: FF65
:small_red_triangle_down: FF67
ui.use_standins_for_native_colors=true (2618)dom.event.highrestimestamp.enabledlight with prefers-color-scheme - see MDN for this standard added in FF67:small_red_triangle_down: FF68
:small_red_triangle_down: FF70
:small_red_triangle_down: FF72
:small_red_triangle_down: FF74
:small_red_triangle_down: FF78
isPointInPath and isPointInStroke still use the white-canvas:small_red_triangle_down: FF80
BaseFonts (non Android)kBaseFonts and kLangPackFontslayout.css.font-visibility.level = 1:small_red_triangle_down: FF82
2020
...
MediaDevices is a different API but a tool like WebRTC JavaScript library implements the Mediadevices API into WebRTC.
One thing that prevents me from using fingerprinting on Firefox for Android is the screen resolution thing. It makes no sense to blow a webpage up to full resolution when there's no way my mobile phone will display it properly. If the pref would disable that particular identifier if it's a mobile version of Firefox it would make so much more sense.
Would it be possible to include a version of the user.js that has privacy.resistFingerprinting set to false? I did the setup in my user-overrides.js, I just think i might miss changes made in the future. Just an idea for ease of use.
Edit: or another idea that might be a bit over the top: Developing an application that generates a user.js file. With preset loading/saving
Thanks Pants! Just passed along the info :)
Hmm ya, I either wasn't clear with what I said or it was misinterpreted a bit.
After linking the ctrl bug I proposed possibly using a different profile for google apps if the bug was preventing them from keeping RFP on. The mention of the privacy API being able to use it was more of a suggestion towards, in the future, uBO and other extensions might be able to quickly turn it on/off.
I agree it's not a solution, but if someone's not willing to keep RFP on because of a bug like this, it's a reasonable alternative in an isolated profile to be able to quickly toggle it on/off as needed.
Just did, thanks :)
not sure what you mean by "affect" but I just tested with a japanese FF63 and the string in the brackets is in japanese characters even with RFP enabled.
They have a test for this but that test most likely only ever runs on en-US versions and therefore they didn't notice the problem.
correction!
during testing a prompt came up at one point asking me this:
言語設定を英語に変更すると、個人情報の特定がより難しくなりプライバシーが強化されます。英語版のウェブページを表示しますか?
Obviously I had no idea what that means and clicked the button which I assumed would be "cancel" because I thought it's something Activity-Stream or telemetry related.
Turns out this translates to
Changing the language setting to English will make it more difficult to identify your personal information and enhance your privacy. Do you want to view the English version of the webpage?
and was triggered by me enabling RFP. Clicking the other non-cancel button and testing again shows that RFP then spoofs the timezone string correctly in english as (Coordinated Universal Time)
I am not sure if this is relevant here, but i have heard suspicion that enabling privacy.resistFingerprinting leads to higher amount of Google Captchas with them being more difficult. For me this only had the result that I started closing pages whenever they prompted me to fill a Google Captcha.
Most helpful comment
I am not sure if this is relevant here, but i have heard suspicion that enabling
privacy.resistFingerprintingleads to higher amount of Google Captchas with them being more difficult. For me this only had the result that I started closing pages whenever they prompted me to fill a Google Captcha.