From 42fa94fb53d69165f8e63fde5362715710263fc9 Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Sun, 5 Dec 2021 12:37:43 +0000 Subject: [PATCH] Updated 3.1 Resetting Inactive Prefs [Scripts] (markdown) --- 3.1-Resetting-Inactive-Prefs-[Scripts].md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/3.1-Resetting-Inactive-Prefs-[Scripts].md b/3.1-Resetting-Inactive-Prefs-[Scripts].md index e002dee..c6c7e39 100644 --- a/3.1-Resetting-Inactive-Prefs-[Scripts].md +++ b/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 8000). +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) or been DEPRECATED (Section 9999) 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`.