Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.
Won't open homepage on open, won't open web pages from the menu 'open new window', Can't open menu button
Ok, since update to version 31.0, I have been having some problems. I have tried doing everything stated in the support page about resetting, reinstalling, safe mode, restarting pc etc. First problem, when I open Firefox no web page loads. It just says New Tab and a blank white page. If I press the home button I am taken to my homepage which is google.
Second problem, when I right click on a link and the menu pops up, if I click open in new window, a new window opens but it just says New Tab with a blank page and no URL information, just blank.
Third problem, the Open Menu button just doesn't work at all. You can click all you like, that thing is not opening.
I am really stuck as to what to do. I have only been using Firefox for about a month and t was good until these problems. If I can't resolve it, I will have to use another browser as it is really annoying.
I am using Windows 8.1 by the way and have scanned my computer thouroughly for both virus's and malware.
Alle Antworten (10)
Hi zenithtwc, have you tested the ESR version for your deployment? It still is based on Firefox 31, however: http://www.mozilla.org/firefox/organizations/
Welcome to the club! I have all your stated issues. I may as well add these issues as well since I'm here and didn't mention them:
I can't reopen closed tabs using the keyboard shortcut, the under the history menu:
- Restore Previous Session is greyed out
- Recently closed tabs is greyed out
- Recently closed windows is greyed out
- Can't Reset zoom with shortcut key or via View->Zoom->Reset
Same for you, Espie?
So far no response at all on the bug thread...
Nothing on this? Basically half the browser functionality is not working, and we get the sound of silence? There's a large number of people struggling with this - are you even taking this seriously?
GOT IT WORKING!
Credit to yeti1983 for this one. Switched the desktop theme back to a Windows standard theme and restarted Firefox. BANG! Everything working 100%!
I had downloaded and installed a Microsoft theme mind you, not some funny hack theme of any kind. I got it from Microsoft themselves: http://windows.microsoft.com/en-ZA/windows/themes
Great work RuggeroSB!
This has pointed me in the right direction. I did some scans of the registry before and after changing the theme. You can change it to any of the "Windows Default Themes." These all worked as well. So the downloading isn't necessary.
A registry key was missing, as seen below. There were many others missing too, but this was the one that blew up the browser if it was deleted. This resulting in the home page not loading, and the hamburger menu button from not opening. :)
Apply the following registry below and WALLAH!
Most importantly the warning for editing the registry...
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. I cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
Windows Registry Editor Version 5.00
It's a bug and it's fixed in FF33+. Simple workaround: https://bugzilla.mozilla.org/show_bug.cgi?id=1065998#c33
Is anybody here who is reporting this issue (links or bookmarks won't open, but some do some of the time) using any OS other than Windows 8.1?
I strongly suspect this is a Windows 8.1 problem, though there may be TWO problems that act similarly.
Hi supmozilla, the problem in this thread severely affects the UI of Firefox users who have a custom Windows 8.1 theme downloaded from Microsoft. If you have a custom theme, try the workaround here: https://bugzilla.mozilla.org/show_bug.cgi?id=1065998#c33
If you are using a built-in theme, then probably you have a different issue, so please start a new question here:
Scroll down past suggested article if they are not relevant to continue with the form.
I have since discovered that that the same issue occurs using other browsers, so those references are not the solution--nor is it a Firefox issue.