Specifically, when you open a reasonable number of tabs in any browser, the tabs look like this. However, as my friend has just imported all of his tabs and bookmarks over from Chrome to Firefox, he has an immense number of tabs open right now; in Chrome, he can see all the tabs at once with its UI. On Firefox, however, it keeps things actually legible by not squashing the tabs so obscenely.

"Okay, so I need some help. I've noticed Firefox doesn't show all tabs like Chrome does. Instead it shows a few, and makes me press a button to see more. Please, tell me there's a way to fix that."

I pointed out that this was an accessibility thing (being able to actually see and read the tabs is a useful feature) and they said it was "not good enough". Further explanation of basic things such as using their scroll wheel to scroll through their tabs, or double/triple clicking on the left/right arrows to jump by page or start/end, or using the Ctrl+# shortcuts, are all tools at their arsenal, but that also was not good enough. Personally I'm a 1,000-2,000 tabs kinda person and manage just fine with those instead of having each tab be literally a pixel wide, so I've never looked for an addon to crush all the tabs together like Chrome does, and my attempts at searching the extensions and themes has come up with nothing.

Is there something like this in the about:config page perhaps, or a convenient theme/extension/addon/plugin/etc that my friend can install to feel comfy using Firefox again?

Highlights We were able to disable some Spectre / Meltdown JIT mitigations! Nightly-only for now. These were mitigations we deployed years ago to protect users against various timing ...

Kind reminder that uBlock Origin, an efficient blocker built by gorhill (Raymond Hill), works the best on Firefox. Spread the word!

Is Firefox ESR more stable? Uses less memory? Have you tried it?

May and June were good months for Firefox's Speedometer performance compared to Chrome. We're closing in while Chrome seems fairly static. In this visualization, lower in the graph is better. From https://arewefastyet.com/win10/benchmarks/overview?numDays=60.

Preferable wouldn't require rooting the phone, but curious to hear if there is a way that requires rooting also.

Looks like the cookie banner blocker, originally scheduled for Firefox 114, didn’t make it into today’s Firefox 115 either. Brave and DuckDuckGo already block cookie banners.

For Firefox, we need to rely on uBlock Origin. Unfortunately, there’s no uBlock Origin for Firefox on iOS.

https://www.mozilla.org/en-US/firefox/115.0/releasenotes/

Just wanted to write down my appreciation for the "Firefox Translations" extension and make people who might find it useful, but missed its announcement, aware of it.

For the people who haven’t heard about Firefox Translations it does local translation from one language to another.
Works on the entire page or just whatever you select.

Not having to offload the task to say google translate or some other company is a great win for privacy and anti-tracking.
It is yet another reason why I’m still on Firefox all these years later.
On any other browser(vast vast majority) this would be online and data mined.

It can’t compete with google translate on number of languages right now, but for a lot of people I’d imagine it’s pretty useful in its current state.
Hopefully additional languages will be added with time.

More information about it here if you want to know more.

Starting July 11, 2023, Pocket users will be prompted to transition to a Firefox account in order to log in and access their Pocket account. Aside from changing how you log in to Pocket, this does not affect your saved items. While optional at first, the transition to a Firefox account in order to log in will be required by August 15, 2023.

For Pocket Premium subscribers, converting your account will not impact your subscription.

On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵