Updated 3.5 prefsCleaner (markdown)

Thorin-Oakenpants 2022-01-30 10:47:38 +00:00
parent 4db82bfcd1
commit ff0cc2b2a2

@ -1,28 +1,26 @@
🟩 Previous: [Apply & Update & Maintain](https://github.com/arkenfox/user.js/wiki/3.4-Apply-&-Update-&-Maintain) 🟩 Previous: [Apply & Update & Maintain](https://github.com/arkenfox/user.js/wiki/3.4-Apply-&-Update-&-Maintain)
🟥 Summary: **ALWAYS run prefsCleaner after updating** 🟥 Summary: **ALWAYS run prefsCleaner after updating**.
--- ---
🟪 The Issue 🟪 The Issue
Over time, Firefox deprecates prefs, and arkenfox also removes prefs or makes them inactive (commented out). It does this because they are no longer needed or may cause issues Over time, Firefox deprecates prefs, and arkenfox also removes prefs or makes them inactive (commented out). It does this because they are no longer needed or may cause issues.
For the duration of each ESR life cycle For the duration of each ESR life cycle:
- `6050s` - we keep a list of prefs removed by arkenfox - `6050s` - we keep a list of prefs removed by arkenfox
- `9999s` - we keep a list of prefs deprecated by firefox - `9999s` - we keep a list of prefs deprecated by firefox
A master copy of everything that has ever been in the arkenfox user.js but is no longer, is kept up to date in our [cleanup script](https://github.com/arkenfox/user.js/blob/master/scratchpad-scripts/arkenfox-cleanup.js) A master copy of everything that has ever been in the arkenfox user.js but is no longer, is kept up to date in our [cleanup script](https://github.com/arkenfox/user.js/blob/master/scratchpad-scripts/arkenfox-cleanup.js).
So these removed, deprecated and inactive prefs should be reset - to avoid issues and keep things tidy. Doing it manually is time consuming and prone to human error So these removed, deprecated and inactive prefs should be reset - to avoid issues and keep things tidy. Doing it manually is time consuming and prone to human error.
🟪 Solution 🟪 Solution
The solution is simple. Script 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. The solution is simple. Script 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.
And that's exactly what the `prefsCleaner` script does And that's exactly what the `prefsCleaner` script does - so ALWAYS run prefsCleaner, with Firefox closed, after each update.
So ALWAYS run prefsCleaner, with Firefox closed, after each update
--- ---