Firefox lost 50M users since 2019

Until version 89 reaches ESR I will continue to use Waterfox classic with XUL addons archive. Not only is faster but I have more addons

All your addons are not everyone's addons. Some people have different, or more, or more specific addons

There are addons that disappeared and are not possible to do today. And maybe you can do something similar, even if clunkier or slower. But a lot of developers have moved anyway, which created holes in the ecosystem

And just having to go and find replacements was difficult since it took a lot of time for addons to reach parity. And people have a day job to get on with

TreeStyleTab still breaks today, sometimes the side bar disappears or is empty

I had an addon that would highlight all bookmark link in all pages, including google results, and on mouse over would show the tags and description. Can you find a similar now?

>The constant nonsense UI redesigns that come about with every new update. The instability, and ridiculous resources consumption. The slowness and slugishness.

>I want a browser that works, respects my privacy, stays out of my way and lets me get shit done. A browser built for professionals, by professionals. I want a consistent UI that remains stable over time. I'm easily willing to pay for such a browser.

>Firefox used to be it, but I no longer feel like it is. Any suggestions for what to try next?

That's my experience as well. I was using FF from v 1.0 back in 2004. Upgrade to Quantum almost gave me a heart attack because it ruined majority of addons and disabled custom themes. Upgrade to "megabar" was a final straw for me. I've spent ~ 3 hours, but finally migrated to Pale Moon ... and it's like I'm back in 2004. Even Noia theme is working again.

FF, in my opinion, went full circle: from being the most functional and the most customizable browser to being the new IE6. There are no redeeming qualities left really.

I think a part of it could be explained by the way things have been in recent times.

As of July 2021 (according to the linked metrics), ~25% of the displays used are 1366x768px while ~40% of them are 1080p. Yet when the "Proton" refresh aimed to promote usability and while certain level of cross-platform was reached, the increase of padding simply made the experiences of people using displays with "less than optimal" resolutions worse. While the proton's hidden and "unsupported" compact mode had a decent height for a 14" FHD display, the same did not look as good on my 15.6" display with the same resolution. When I complained on reddit like many others about the increase in whitespace, I don't think it was given what I believe to be a proper consideration. Why would the main menu be bigger despite having fewer items? And where are the icons? It was a concern back when it was in nightly and many of the concerns remain now even though it has had a stable release.

Another thing that is problematic is the colour-scheme. The newer style incorporates less contrasted colours and does away with what made the preceding Photon design better in certain ways: look at how the tabs on FF used to have a markedly different colour than their backdrop and how there used to be separators between tabs. The fact that the newer design is a bad one somehow eluded those in charge of it and the fact that the contrast between the active tab and its surrounding elements being low being an important issue is an afterthought is telling.

Moreover, the dropdown for the megabar suggestions used to have full-window width but now it is limited to the megabar width for no apparent reason other than looking "cool" (which it does not btw; especially when you compare it to Chromium's counterpart). They introduced the megabar-expansion-on-focus behaviour, kept a config to disable it for a major release or two and then dumped the old one. Also, when you selected multiple tabs, upon a right-click, it used to tell you the count of selected tabs - which no longer seems to be the case. Needless to say, looking at userChrome.css to be _the_ solution for undesirable changes would not work well for anyone in the long run.

Firefox, unlike Chromium-based browsers, does not support XDG base dir spec. It does not bother me very much and neither does FF flickering every once in a while on my main system. What bothers me is that with each new release I feel like FF is losing bits of its magic. Back when FF Quantum was released and was stripped of what many considered the level of flexibility which appealed to them, I was concerned but ultimately accepted it. But this time around the changes feel like marketing speak. Mozilla already has a discourse instance but post-Proton-release they also have a crowdicity instance...

The way things have been going is genuinely upsetting and many users are just reacting to that.

just extend (heh) the current extension API with the most important missing ones like e.g. a hideBuiltinTabBar().

It is actually slightly more complicated since some stuff depends on the main tab bar being visible (or so they say, my Firefox works nicely even if I disable the main tab bar using a CSS hack.)

That sucks, but take the time to imagine what might be going on on the other side.

There's a dev running an experiment to whitelist more combinations of the huge space of (Device, CPU, GPU, OS, OSVersion, Browser, BrowserVersion) to use that feature. What would you do after seeing that the metrics show that most of the users on your experiment had a bad experience? In that case you'd want to rollback your experiment right away and figure out what's wrong. You really expected all, if not most of the combinations you selected to actually work well, but it's apparently not the case.