Git/firefox-user.js
1
0
Fork 0
mirror of https://github.com/arkenfox/user.js.git synced 2024-11-25 03:51:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated 3.1 Resetting Inactive Prefs [Scripts] (markdown)

Thorin-Oakenpants 2021-12-05 12:49:22 +00:00
parent 6c2cc36f8e
commit 465b8c6900
1 changed files with 16 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,13 +1,14 @@
: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) or been DEPRECATED (Section 9999)
:small_orange_diamond: The Issue
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`.
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 or made INACTIVE (i.e commented out) such as DEPRECATED prefs (Section 9999)
So the issue is :question: How do you make sure all the INACTIVE/REMOVED prefs in **your** `user.js` have been reset in about:config? Over time you **will** miss something - doing this manually is time consuming and prone to human error.
So **some or all** of these REMOVED and INACTIVE 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`.
### :small_orange_diamond: The Solution
So the issue is :question: How do you make sure all the REMOVED and INACTIVE prefs have been reset in about:config? Over time you **will** miss something - doing this manually is time consuming and prone to human error.
:small_orange_diamond: The Solution
The solution is simple. Automate it, and reset **every single pref** in the user.js regardless of whether it is active or inactive. Then restart Firefox and all your ACTIVE prefs are reapplied. The end result being all your INACTIVE ones have been reset.
@ -23,7 +24,7 @@ Think of it as an opportunity to increase your automation by setting those manua
---
#### :small_blue_diamond: prefsCleaner
:small_blue_diamond: prefsCleaner
Download the prefsCleaner [for Windows](https://raw.githubusercontent.com/arkenfox/user.js/master/prefsCleaner.bat) or [for Linux/Mac](https://raw.githubusercontent.com/arkenfox/user.js/master/prefsCleaner.sh) and **run it in your profile directory with Firefox closed**.
@ -56,4 +57,12 @@ The REMOVED script is the ONLY single point of reference for everything we once
<sup>1</sup> Blocking Firefox from the internet ensures it cannot act on your reset preferences in the period before you restart it, such as app and extension auto-updating, or downloading unwanted components (system addons, GMP etc). It depends on what you're resetting and how long before you restart.
</p></details>
</p></details>
testing: ignore me
🔵 eh
🟢 meh