Exit Customize doesn't work - other questions...
Firefox updated to Beta 29 (i didn't do it x_x) and everything is confusing me right now. Actually pissing me off to be honest. I was playing around this new, tried to customize it but didn't work. I followed this page and nothing. https://support.mozilla.org/en-US/kb/customize-firefox-controls-buttons-and-toolbars the Exit Customize doesn't work at all. I have to quit firefox using Alt+F4 and start all over. So, that doesn't work for me. How do I go back to the previous version of Firefox or how do I undo this Beta 29 thing? I really don't like it.
Усі відповіді (4)
I can't find the Stop button, like when you want to stop a page from loading.
Note that if you were using a Release version of Firefox you would not get a update to a Beta build as you were likely on the Beta channel due to having installed a Beta build of a Release at some point.
The full Firefox 28.0 release setup can be found at http://www.mozilla.org/en-US/firefox/all/
The Firefox 29.0beta 1 is the closest to Release to currently have the new Australis ui which probably should not have been put on Beta channel with 29.0 early this week when it was still not quite finished.
If you want to continue to be testing the Firefox 29.0 Beta builds (there can be say six to twelve) then this extension may help bring some familiarity back. https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/
Змінено James
Full version of 20.0.1 automatically installed today and that's not the only customization they screwed up.
There's no longer a back button and I can't get my menus and my bookmarks to go back where I had them. I had them where I want them. In fact it looks like there's no customization at all, you can only have the customizations if the developers approve.
Is there any way to revert to prior updates without completely blowing Firefox away and doing a clean install of an older version.
Where can I find the older versions to do a clean install?
Змінено JBS1949
You can check for problems with preferences.
Delete a possible user.js file and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.
You can check for problems caused by a corrupted localstore.rdf file.
Create a new profile as a test to check if your current profile is causing the problem.
See "Creating a profile":
- https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem