Tabs on top again after update v65 in Jan 2019
I hate and avoid updates and now I am reminded why: tabs are back on top, where I don't want them.
Is there any help from someone how I can put them back underneath the address/search bar? Or move the address and search bar back to the top?
Additional System Details
- Shockwave Flash 32.0 r0
- User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0
See this thread for updated userChrome.css code for Firefox 65 to move the tabs to the bottom position.
- [/questions/1248277] Reposition Tabs at bottom, directly above web page in Firefox 65.0?
Hi, thanks for trying to help, but this is beyond me. I am not a programmer. And all I am trying to do is get what I had before the update. If all this is so easy to implement using Chrome, why is it not part of Firefox? Also, I would prefer the Command line, then Address bar, then tabs and then bookmarks, the way it was sorted before. Something that was very easy to do previously. Is reprogramming FireFox really the only way? Thanks again for your help.
You were very likely using some userChrome.css to put the Tab Bar back on bottom in 57.0 to 64.0.
Firefox has had the Tab Bar on top ever since Firefox 29.0 and on because it required two massive code stacks to be maintained in parallel, which was expensive, bug prone, and slowed down Firefox. It was possible to put it on bottom with an (legacy) Extension up till the Firefox 57.0 Release and later not being compatible.
From Fx 57.0 and on you needed to use some userChrome.css however as of Firefox 65.0 and later versions there were some minor changes that made the code used to put tab bar on bottom before in need of an update.
Modified by James
"You were very likely using some userChrome.css to put the Tab Bar back on bottom" Erm, no, I don't even know what any of this means. All I know is that the tab bar was in between the bookmarks and the address/search bar. And all I would like is to have that back. It is true that - for a good reason as we can see now - I put off updates as much as possible since they became less and less beneficial for me. But thanks for trying to help.
Which version of Firefox did you update from when Firefox 65 was installed?
Firefox 29 (Australis UI) up thru Firefox 56 didn't have a preference for disabling "Tabs on Top", although many users installed the Classic Theme Restorer extension to "add" that preference to the Australis versions. CTR is dead for the Quantum versions of Firefox 57 and beyond. So if you haven't been using a userChrome.css file in Quantum, I suspect that you were using a real old version of Firefox - namely Firefox 56 or earlier.
Please read the articles that cor-el and James hyperlnked in their answers and create a userChrome.css file - it isn't all that hard. Reading an comprehension are all that is really needed to effect the customizations that are needed to move the Tabs to the bottom.
Thanks for trying to help. I appreciate the help effort and simply can't understand why a working solution was abandoned. That, after all, was my primary reason to choose Firefox, the add-ons, enabling me to make the browser look and behave how I want and not how the programmers want. This ability is gone to a large extent. "Which version of Firefox did you update from" I don't spend efforts on version control. It was the one before that, since after clicking not now for a few weeks I update eventually, even if it means that less stuff works. "many users installed the Classic Theme Restorer" I had that until changes to Firefox meant it no longer worked. "I suspect that you were using a real old version of Firefox" No, I was not. Adn yes, I found this CSS thing - but it doesn't do what people here say it should do. I must have found this in the past and forgot about it. Finding the correct profile of Firefox and digging deeper to find this and compare the contents is not just a 2 minute job for someone who does not do this more than once every few years. So maybe one day someone will be able to come up with an add-on or a working solution. Maybe then I will stop using Vivaldi, Maxthon and Chrome again.