Also I didn't say I should write in the browser, I said the browser should let me collect information from the internet in such a way to make my job easier
Firefox have also the "Browser Toolbox"[2], homologous to the web development tools, that one can use for to explore the css of the UI, select elements, etc, and modify them for to see how would look the modifications before to put them within the userChrome.css
The tabs I think that are under the id=TabsToolbar, so an #TabsToolbar{ display: none !important; } or similar should work, in addition to correct with other css params the space that it leaves.
Note: What happens is they change things from time to time, and after an update one have to correct the css again, I warn.
[1] https://github.com/Aris-t2/CustomCSSforFx
[2] https://firefox-source-docs.mozilla.org/devtools-user/browse...
Hiding it in usercss isn’t supported and is liable to disappear at any point (say, the developers decide they’re tired of maintaining some part of the code that makes the custom usercss flag work). It serves the purpose for now, but cannot be relied upon in the long term and as such is a hack.
Unless there's something I'm missing re: Mozilla's history/market-positioning?
Aside from that I just think it’s a good idea to push for implementation of basic functionality like hiding bars that don’t pair nicely with popular vertical tab extensions. I shouldn’t need to resort to usercss mods to do something that simple.
The problem here, though, is that the core browser becomes the lowest common denominator. When I set up a computer, I don't want to have to spend all day getting my browser into a usable state. I don't want to have to recommend Firefox with the asterisk that you need half a dozen plugins to make it good. I don't want to wake up and find that the tab management plugin I like has been bought out by a sketchy company that's now using my browser as a proxy server for scrapers.
And having a browser that's not minimalist is known to work. We have tabs today, for instance, because of the fine folks at Opera pushing the boundaries of what the browser can be. Not every browser needs every feature, but some things are just good quality of life improvements that plugins should be able to disable (versus requiring plugins to add all nonessential features).
You want a browser that can preload plugins on install with a config.
It's also funny how you bring up innovation. The thing is plugins enable much more innovation because a plugin can be made by a single person with a great idea and relatively little knowledge. Just imagine everyone who wanted to try out some innovative new feature would have to build their own browser first.
I don’t have a need to efficiently write an article in a browser - or code within a browser which is more my thing. I have a dedicated IDE for that, and leave browsing to browsing.
Browsers imo should just be browsers and leave the end user applications to the web app developers, plugin developers, etc. So in that sense I’m happy with where they are, and very happy they are doing their own stuff rather than being another Chrome-based browser.