Git/firefox-user.js
1
0
Fork 0
mirror of https://github.com/arkenfox/user.js.git synced 2025-02-16 20:11:15 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated 3.1 Resetting Inactive Prefs [Scripts] (markdown)

Thorin-Oakenpants 2021-10-10 23:58:06 +00:00
parent 8ce9c816f6
commit cbe22392c0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
3.1-Resetting-Inactive-Prefs-[Scripts].md

@ -1,7 +1,7 @@
:exclamation: Read the instructions & backup your profile before running any of the scripts mentioned here
### :small_orange_diamond: The Issue
Our [changelogs](https://github.com/arkenfox/user.js/search?q=label%3Achangelog&type=Issues&utf8=?) are lists which contain, among other things, information on prefs that have been REMOVED, made INACTIVE (i.e commented out), DEPRECATED (Section 9999), or become REDUNDANT/CONFLICT with `privacy.resistFingerprinting` (RFP) (Section 4600).
Our [changelogs](https://github.com/arkenfox/user.js/search?q=label%3Achangelog&type=Issues&utf8=?) are lists which contain, among other things, information on prefs that have been REMOVED, made INACTIVE (i.e commented out), DEPRECATED (Section 9999), or become REDUNDANT/CONFLICT with `privacy.resistFingerprinting` (RFP) (Section 8000).
So **some or all** of these REMOVED, INACTIVE, DEPRECATED, and REDUNDANT prefs **need to be manually reset** in `about:config`, depending on your configuration. And over time, the list builds up. Some are harmless (deprecated items will have no effect), but others are vital (prefs and sections are INACTIVE for a reason, so it pays for your `prefs.js` to be in "sync"). Add to this any prefs you may have made inactive yourself. A REMOVED pref is particularly tricky as it is no longer referenced in the `user.js`.