Unified Stop Reload Go button comes to Firefox 4

Pieces keep fitting in for the Firefox 4 theme refresh. Recent development nightlies now feature the planned stop-reload-go button next to the location bar.

When the page is loaded, it becomes a reload button.

A stop button while loading.

And , if you edit the web address, you get the go button.

While it should make more sense to new users, this is no doubt going to anger more than a few long time Firefox users used to clicking next to the back button to reload or stop the current web page.

However you can take the buttons back to their previous location through the Customize Toolbar window: open the Minefield (Firefox) button, and select Toolbar Layout… in the Options menu. The buttons are decoupled and you can drag them at will.

You can also take a half-way approach by moving the unified button to the left of the location bar with this user style. You will need the almighty Stylish extension.

UPDATE: It is actually possible to decouple the reload, stop and go buttons, as noted in the comments. The miserably wrong statement has been updated to reflect this. Thanks to all commenters!

20 thoughts on “Unified Stop Reload Go button comes to Firefox 4”

  1. Percy, it’s quite easy to move the Stop/Reload combo back to the current position via the Customize menu. It was maybe added in a later nightly build than the one you used?

  2. @ Stan

    Its been in the nightly builds since it landed. Using the “Customize” menu the buttons are purposely decoupled for the purpose of moving them until that window is closed again.

    Reload and Stop has to be together and on the right side of the Location bar in that order for it to activate. If the order is reversed, Reload and Stop will merge but it will not be attached to the Location Bar.

    1. Seriously, people push too much about their greasy scripts and stylish… styles.

      I see time and time again how people create workarounds through those channels rather than take a quick gander at the settings.

    1. You can find all info in the bug for it.

      “As stated above, Mozilla is waiting on stuff in GTK to land so they can use it
      to implement the features in a SANE way that doesn’t break things.

      There’s no good way to fix bug #513159 on Linux at the moment, but there WILL
      be, however not in time for FF4 so Mozilla has decided to wait until they do it

  3. Still GUI is too big. I mean dam look at that huge orange minefield button. I wish it was lower to give us few pixels of webpage (very important on netbooks) on screen. I would see orange menu button on left side of tabs and like square. To make it simple: Give us some more spaaaaaaaace. Cause its sad, Opera is very minimal, Chrome is minimal too, so why the hell my favorite firefox cant be ? Its like huge cow taking half the screen.

  4. i also think that the gui is too big! the should remove the Text from the Orange button and put a firefox logo into it.. and then they should move it next to the tabs.. and then it would need a lot less space…

    i also hate the blueish look.. i would love a glass look or just white..

  5. Hummmm… the new Firefox 4 is like a shiny new car without transmission and brakes …. it turns on fast, can not change gears and can not find the brakes! … I have tree tabs open and waiting to load … one did not load right and pop-ups sometimes populate the tabs bar ….. one is a silly loop of advertising, another is a news pop up … I mean running continuously ….
    Who had all those great ideas at Mozilla? …. why you don’t just lock us out of the computer and let advertisers roam at will! …. do you expect us to just sit and watch our computers play on their own and us watch it like TV? … get real! … exclude advertisers and kill the pop ups plus place a big stop button where it belongs …
    As it is now I am willing to pay for a browser that does what I want!

  6. Beyond the stop button having a new location, has its functionality changed?

    I am running motion, an open source camera app, and it continuously streams .jpgs to my browser. Up until now, hitting the “STOP” button, if a complete image was loaded, would stop loading the stream BUT LEAVE THE CURRENT IMAGE IN PLACE FOR VIEWING.

    Try as I might, I can’t get that feature to work anymore; now *every* time I hit stop the page goes blank.

    Can someone comment?

Comments are closed.