Open Bug 1490728 Opened Last year Updated Last month
Improve discoverability/explanation of RFP
When Resist Fingerprinting is enabled, we will override prefs and lock down other options. For a truly hard-core RFP mode, we need to do a better job of identifying what prefs we need to override. But we should also enable some form of discovery for users - a console notification or a tab or something that explains what RFP is doing (on the web) and what it has negated in the browser (user-set prefs, possibly disabling extensions if we decide to do that, etc)
Whiteboard: [tor][fingerprinting] → [tor][fingerprinting][domsecurity-backlog1]
This option should NOT override user defined general.*.override values, e.g. general.appversion.override general.oscpu.override general.platform.override general.useragent.override
Note: 1. This bug is likely to require UI/UX support. 2. We need to trace code base to identify all the prefs overridden by RFP.
Whiteboard: [tor][fingerprinting][domsecurity-backlog1] → [tor][fingerprinting][domsecurity-backlog1][fp-triaged]
You need to log in before you can comment on or make changes to this bug.