Git/firefox-user.js
1
0
Fork 0
mirror of https://github.com/arkenfox/user.js.git synced 2024-12-22 00:55:08 +01:00
Code Issues Packages Projects Releases Wiki Activity
Page: 3.5 prefsCleaner
Pages
1.1 To Arkenfox or Not 2.1 User.js 2.2 Backup 3.1 Overrides 3.2 Overrides [Common] 3.3 Overrides [To RFP or Not] 3.4 Apply & Update & Maintain 3.5 prefsCleaner 4.1 Extensions 5.1 Updater [Options] 5.2 Troubleshooting Appendix A Test Sites Appendix B Test Sites [Fingerprinting] Appendix C References Home
6 3.5 prefsCleaner
Thorin-Oakenpants edited this page 2022-02-19 20:37:48 +00:00

🟩 Previous: Apply & Update & Maintain

🟥 Summary: ALWAYS run prefsCleaner after updating.

🟥 Warning: DO NOT DELETE PREFS.JS. prefs.js is a runtime file that includes more than just your pref changes.

🟪 THE PROBLEM

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:

  • 6050s - we keep a list of prefs removed by arkenfox
  • 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.

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.

🟪 THE SOLUTION

The solution is simple. Script it, and reset EVERY 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 - so ALWAYS run prefsCleaner, with Firefox closed, after each update.

🟩 Next: Extensions