Updated 1.4 Troubleshooting (markdown)

Thorin-Oakenpants 2020-10-20 12:37:48 +00:00
parent 17ac2335fd
commit 64be5ba819

@ -4,6 +4,22 @@ Besides asking and guessing, the only way to find the cause(s) of why something
We have an "unofficial" sticky issue [here](https://github.com/arkenfox/user.js/issues/391) for prefs that can break extensions We have an "unofficial" sticky issue [here](https://github.com/arkenfox/user.js/issues/391) for prefs that can break extensions
### :small_orange_diamond: Check your `"parrot"` and console
When you modify your user.js, such as adding any overrides, sometimes syntax errors happen. Open about:config and check your `"parrot"`. Arkenfox uses `_user.js.parrot` throughout the user.js. You can use any pref name you like, as long as it's different (to avoid confusion). Note: [not all](https://blog.mozilla.org/nnethercote/2018/03/09/a-new-preferences-parser-for-firefox/) syntax errors cause the user.js parsing to be aborted. After Firefox opens, open the Browser Console (Ctrl+Shift+J) and check for any other errors.
example
```js
/* my overrides */
user_pref("canary.in.a.coalmine", "overrides: starting"); // parrot, canary, whatever you like
user_pref("toolkit.legacyUserProfileCustomizations.stylesheets", true); // userChrome/userContent
user_pref("ui.key.menuAccessKey", 0); // disable alt key toggling the menu bar [RESTART]
user_pref("browser.tabs.extraDragSpace", false); // stop theme turning drag space on
user_pref("canary.in.a.coalmine", "overrides: success");
```
### :small_orange_diamond: Use the Browser Console ### :small_orange_diamond: Use the Browser Console
Open the Browser Console (`Ctrl+Shift+J`) and clear it. Then repeat the action / task that is not working as intended, and see if the console logs anything. If it does but you can't decipher what it means, feel free to post the error message in a new issue and maybe we can help. But do try and dig a little deeper first Open the Browser Console (`Ctrl+Shift+J`) and clear it. Then repeat the action / task that is not working as intended, and see if the console logs anything. If it does but you can't decipher what it means, feel free to post the error message in a new issue and maybe we can help. But do try and dig a little deeper first