My "Refresh' & "Stop" buttons are gone now that I upgraded. Where did they go?
Hi, Thank you for your help. I recently upgraded to your 4.0 version, as offered. I have always had an area that had buttons to click that were for "Refresh Page" and "Stop Page" and they were by the "Forward and Back Page" buttons. (The "Forward and Back" buttons are still there.) I have looked everywhere for these buttons. Where did they go? Am I missing something? Did you move them somewhere else?
I even moved my Tabs so they weren't at the top of the page, thinking that maybe the Tabs were hiding them, somehow. But the buttons for "Refresh and Stop" were not there, either.
Any help would be greatly appreciated Thanks, Winnie
All Replies (3)
Firefox 4 uses a combined Stop/Reload/Go button that is positioned at the right end side of the location bar.
During the page load process it shows as a Stop button and after the loading has finished the button is changed to a Reload button.
If you type in the location bar then that button becomes a Go button.
You can middle-click that Reload button to duplicate the current tab to a new tab.
To move the Stop and Reload buttons to their position to the left of the location bar you can use these steps:
- Open the Customize window via "View > Toolbars > Customize" or via "Firefox > Options > Toolbar Layout"
- Drag the Reload and Stop buttons to their previous position to the left of the location bar.
- Set the order to "Reload - Stop" to get a combined "Reload/Stop" button.
- Set the order to "Stop - Reload" or separate them otherwise to get two distinct buttons.
the solution posted worked for me as well, thank you
It would be helpful if the Firefox Help menu would provide your answer to restore toolbar default options.
By the way, how do the default options get changed without the user making the change?
Over the past few months, the reload and home buttons have been moved to the URL window a few times through no action of my own, compelling me to find your solution in this forum.
Thank you for providing a way to work around this Firefox problem.