From 4f6eeb59b87166db0ec9ca9d3b9bcc825fff75bb Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Tue, 4 Dec 2018 05:53:40 +0000 Subject: [PATCH] Updated 1.4 Troubleshooting (markdown) --- 1.4-Troubleshooting.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/1.4-Troubleshooting.md b/1.4-Troubleshooting.md index a0ebf11..7504b89 100644 --- a/1.4-Troubleshooting.md +++ b/1.4-Troubleshooting.md @@ -1,5 +1,12 @@ Besides asking and guessing, the only way to find the cause(s) of why something doesn't work as expected, is to **methodically** eliminate preferences. And only after it is confirmed that the user.js is the cause, by replicating the problem in a new profile with no extensions. +### :small_orange_diamond: Tags + +While not 100% definitive, we have included `[SETUP*` tags for troubleshooting (and setting up). Some examples + * `[SETUP-WEB]` can cause some websites to break + * `[SETUP-CHROME]` changes how Firefox itself behaves (i.e. NOT directly website related) + * `[SETUP-PERF]` may impact performance + ### :small_orange_diamond: Use our scratchpad script Before you go on to the laborious task of manual troubleshooting you should try our [troubleshooter script](https://raw.githubusercontent.com/ghacksuserjs/ghacks-user.js/master/scratchpad-scripts/troubleshooter.js) first. In many cases it will be able to either directly identify the culprit or at least narrow it down to a more manageable number of prefs for manual troubleshooting. You can just run the script and follow the instructions but we strongly recommend to watch the [demo video](https://anonfile.com/6eZ9v9d9b6/troubleshooter_vid.zip) first (webm, 62mb, 16m26s).