I don't know whether custom CSS will work in this case. You may be able to find a recipe on the Mozillazine forums if you don't find one here.

I do know it can be done using the Classic Theme Restorer extension. Please see: How to make the new Firefox look like the old Firefox. In the extension's Options dialog, Main tab, "General UI" section, make sure the "Combine stop & reload buttons" checkbox is unchecked.

Thank you! I found separate button, which can be added in any toolbar. But still can not remove it from the right side of the URL box.

P.S. Thank you! But Classic Theme Restorer is not 100% back-getter, it was the first thing which was found via Google.

For example I lost default icons to be colored. And it seems there is no solution. I lost "quit" item from menu and it is a job to findout howto place it back. There is a need to search for bookmarks button, as the old one is not functional, but still in toolbar as a white space.

So, it can do something, but a lot is missed or lost. :(

Hi Asc, I think there is a checkbox in the Classic Theme Restorer Options, Main tab, on the right side under UI Options (sorry for the wrong name, this is from memory) to suppress the stop/reload button that is in the address bar.

For the other issues, hopefully those areas will improve. The extension is under active development and I'm sure the author is getting a lot of suggestions.

"I lost "quit" item from menu and it is a job to findout howto place it back."
In the default Firefox 29 user interface.

• Hit the Alt key to show the Menu Bar. Exit is still at the bottom of the File menu.
• In the lower-right corner of the new Menu Panel (hit the "3-bar" button on the right-side of the Nav Bar) there is as "electrical switch" icon for Exit Firefox.

I am trying to configure Firefox 29 to my tastes without using an all-in-one "retro" extension like the Classic Theme Restorer extension. I have been through 4 other UI design changes with Firefox in the past 12 years, although this is the first real major change; who is going to fix the problems that come about when users install other extensions that are made (rightly so) for the default user interface and those extensions don't work properly with CTR?

Is Aris, the developer of CTR, going to fix CTR every time an extension that has a problem with CTR? Or is every developer creating a new extension for Firefox going to have to "write" for both the default and CTR? What about existing extensions; are those developers going to be expected to update AND add support for CTR?
As it is, users find too many quirks or minor incompatibilities as it is. Adding another complicating factor isn't something that I intend on doing; "been there, done that" too often in the past.

Just trying to be a voice of experience and of reason.....