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

Updated 1.4 Troubleshooting (markdown)

Thorin-Oakenpants 2018-12-04 05:53:40 +00:00
parent 2c41b81061
commit 4f6eeb59b8
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
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. 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 ### :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). 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).