Git/firefox-user.js
1
0
Fork 0
mirror of https://github.com/arkenfox/user.js.git synced 2025-02-23 23:41:15 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated 1.4: Troubleshooting (markdown)

Roman-Nopantski 2017-02-24 06:00:42 +13:00
parent 7558a63fd7
commit 5a9219997d
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
1.4:-Troubleshooting.md

@ -7,6 +7,7 @@
* Open Firefox and go to the web page where you can replicate the problem and bookmark it * Open Firefox and go to the web page where you can replicate the problem and bookmark it
* Verify that the problem does not exist in a vanilla Firefox setup. * Verify that the problem does not exist in a vanilla Firefox setup.
3. Set up a profile-master for quick resets 3. Set up a profile-master for quick resets
* Close Firefox
* Go to the `\FirefoxPortable\Data\profile` folder and create an empty user.js file * Go to the `\FirefoxPortable\Data\profile` folder and create an empty user.js file
* Then go up a directory to the `\FirefoxPortable\Data\` folder and COPY the `profile` folder. Rename it `profile-master` (we can use this to quickly restore to a vanilla profile) * Then go up a directory to the `\FirefoxPortable\Data\` folder and COPY the `profile` folder. Rename it `profile-master` (we can use this to quickly restore to a vanilla profile)
4. Make sure the user.js is the cause 4. Make sure the user.js is the cause
@ -22,7 +23,7 @@
7. Halving method (do step 6 or 7) 7. Halving method (do step 6 or 7)
* This method involves re-setting your vanilla profile often (see step 5) * This method involves re-setting your vanilla profile often (see step 5)
* Use this method if you have no idea what section could be the cause. By testing half and then based on the results, testing the next quarter, and then based on those results testing the next eighth etc, you can rapidly narrow it down in four or five steps at most. * Use this method if you have no idea what section could be the cause. By testing half and then based on the results, testing the next quarter, and then based on those results testing the next eighth etc, you can rapidly narrow it down in four or five steps at most.
* With a preset profile (see step 5), edit the user.js and paste in half the sections eg 0100-1400, and save the changes. Restart Firefox and test if the problem exists. If it does we now know it is the 0100-1400 half that contains the culprit. If not, we know it is the 1600-3000 half. For this example the problem didn't occur. * In a reset profile (see step 5), edit the user.js and paste in half the sections eg 0100-1400, and save the changes. Restart Firefox and test if the problem exists. If it does we now know it is the 0100-1400 half that contains the culprit. If not, we know it is the 1600-3000 half. For this example the problem didn't occur.
* In a reset profile, edit the user.js and paste in half the 1600-3200 sections, eg 1600-2500, and save the changes. Restart Firefox and test if the problem exists. If it does we now know it is the 1600-2500 half that contains the culprit. If not, we know it is the 2600-3000 section. * In a reset profile, edit the user.js and paste in half the 1600-3200 sections, eg 1600-2500, and save the changes. Restart Firefox and test if the problem exists. If it does we now know it is the 1600-2500 half that contains the culprit. If not, we know it is the 2600-3000 section.
* Keep repeating these steps to narrow it down * Keep repeating these steps to narrow it down
* You can also use this method to halve big sections such as 2600 * You can also use this method to halve big sections such as 2600