Well, for starters - they need to figure out why all the browser skinners (Edge, Brave, etc) keep using Chromium as a base instead of Firefox. I don't pretend to know the reasons - but I would wager there's some pretty good reasons Chromium is dominating that space.

Microsoft and Google are at total odds with each other - I can't imagine using Chromium as a base sent people skipping down the halls in Redmond.

One thing that they could do is make Firefox at least as responsive on iOS as Safari is.

I know that browsers on iOS are forced to use WebKit (although that might change soon[1]). But Safari is also using WebKit, and the lag that I get in Firefox when opening a new tab is testing my commitment to them.

[1] https://www.macrumors.com/2022/12/14/apple-considering-non-w...

not pissing off power users - who are the only people who use firefox - in an utterly futile attempt to attract the general population.

this plea - that many people had made over the years - falls on deaf ears. mozilla is now ran by the kind of people who knows better than its users what we need, and we're wrong if we disagree.

Important. Firefox got where it was partially because many of us installed it for coworkers and relatives and everyone else, not because ordinary users sat down to try to figure out what browsers existed and which one was better.

Towards the end, Firefox was an easy sell.

And, as you write, today they don't care or even actively resist when we try to help.

Copying Chrome perfectly won't get any their users back.

Funding all kinds of weird side projects won't get users back.

Amazing, resource-efficient skinning might get some people back.

Tree Style Tags and other plugins working amazingly well might get some users back.

And when they start listen and fix the things we report things can improve very rapidly.

There are also probably a number of other improvements that can be done (I've advocated looking into doing the same as asm.js, but with html and css: something like a put meta-tag announcing html-lite or html/asm or something in the head, use a restricted set of css and html that is rendering friendly and only uses these well thought out js-libraries and we will pass your code down a much more efficient rendering branch!)

Bring back the things that made us power users love it and generally start caring more about bug reports.