From 212b6605cf9ae7a034f69a6318f8000b93ce3888 Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Sun, 30 Jan 2022 13:51:07 +0000 Subject: [PATCH] Updated 3.5 prefsCleaner (markdown) --- 3.5-prefsCleaner.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/3.5-prefsCleaner.md b/3.5-prefsCleaner.md index f0f3424..8f48cbf 100644 --- a/3.5-prefsCleaner.md +++ b/3.5-prefsCleaner.md @@ -4,7 +4,7 @@ --- -🟪 The Issue +🟪 **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. @@ -16,9 +16,9 @@ A master copy of everything that has ever been in the arkenfox user.js but is no 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 +🟪 **THE 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 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.