One more new change which is part of progressive rollout:FYI, Firefox 140.0.4 official release coming soon, once more bug fixes:
![]()
Firefox 140.0.4, See All New Features, Updates and Fixes
www.mozilla.org
One more new change which is part of progressive rollout:FYI, Firefox 140.0.4 official release coming soon, once more bug fixes:
![]()
Firefox 140.0.4, See All New Features, Updates and Fixes
www.mozilla.org
Firefox 141 is a small release that only introduces a couple of new features, one of them being the ability to use less memory on Linux systems and no longer requiring a forced restart after applying an update via a package manager.
9to5linux.com
Mozilla introduced tab groups in Firefox some time ago. The feature enables users to sort open tabs into groups to improve manageability. This is done via drag & drop, or by right-clicking on a tab and selecting the "Add Tab to New Group" option from the context menu.
Each group comes with a color and a name, and tab groups work both in horizontal and vertical tab bar mode.
The new feature uses local AI to identify similar tabs to bundle them together in a tab group. Here is how you access it:
- Right-click on the tab group identifier in Firefox.
- Select "Suggest more tabs for group".
- Confirm the terms (once).
- Accept or decline tabs that Firefox identified.
The feature worked considerably well during tests, especially for tabs with matching domain names. If you open several Ghacks articles, Firefox's feature will (very likely) mark all of them for inclusion in a tab group, when you make use of the feature. Mozilla says that the AI reads the titles and descriptions of the tabs for its suggestions.
Good news is that the user stays in control. You can uncheck any tab that you don't want included in the tab group.
Who benefits the most from the feature? Firefox users who use tab groups and have lots of tabs open in the browser. If you want to create tab groups to manage tabs better, this one may be useful to you.
The feature is rolling out over time. You can enable it right away by setting browser.tabs.groups.smart.enabled on about:config to True.
I was reading a reddit thread yesterday, about mkv support in r/Firefox. That's when I found out about an 8-year-old bug report on Bugzilla for supporting mkv container still pending.After all these years....It's a bit silly that it took them so long but it's good that Firefox is going to have this feature.
It's the copy link to highlight feature
![]()
I was reading a reddit thread yesterday, about mkv support in r/Firefox. That's when I found out about a 8-year-old bug report on Bugzilla for a supporting mkv container still pending.
Firefox was my main browser for years (5-6 years ago when I was using my previous laptop), until it started dropping frames while playing 4K@60 YT videos. Meanwhile, videos played fine with both Edge and Chrome. I didn't know about Bugzilla back then, so I made a Reddit thread describing my problem in-detail. I tried so many things from changing GPU drivers, clearing cache/cookies, new profile, etc., but nothing seemed to work. Then one of the mods there created a bug report for me (because I didn't know how) and I chased that bug for six months on Bugzilla until it was resolved (cause was a regression caused by Firefox update). I had already switched to Edge completely at that point.I wish they'd adopt Chromium's window management. Moving tabs to another window is a torture on Firefox.
When I was searching Bugzilla few months ago, I found bugs and feature requests 15 years old still stuck "in progress"...
If I learned something during my use of Firefox it's that Mozilla has a very high priority for fixings bugs they themselves found, and very little to no priority for the bugs found by the users. You can report critical bug, but don't expect it to be fixed before they release 141 another useless feature.
I have reported two issues which still aren't resolved (one was even said to be normal, but it isn't). The first one was reported a year ago (for affected Firefox 128.0), and to this day remains open with P3/S3 and status UNCONFIRMED. The other one never managed to get priority rating or status.Firefox was my main browser for years (5-6 years ago when I was using my previous laptop), until it started dropping frames while playing 4K@60 YT videos. Meanwhile, videos played fine with both Edge and Chrome. I didn't know about Bugzilla back then, so I made a Reddit thread describing my problem in-detail. I tried so many things from changing GPU drivers, clearing cache/cookies, new profile, etc., but nothing seemed to work. Then one of the mods there created a bug report for me (because I didn't know how) and I chased that bug for six months on Bugzilla until it was resolved (cause was a regression caused by Firefox update). I had already switched to Edge completely at that point.
I moved from Brave because I wanted a browser with more control and complete ad blocking experience. It turns out my browser choice is very much limited, eh.I still use Firefox & I still feel it will be a sad day if or when its gone forever & Chromium has a total monopoly - (BTW I hate playing Monopoly)
- Fixed a startup crash experienced by some Linux users with outdated NVIDIA drivers. (Bug 1978911)
- Fixed a regression that caused canvas objects to be draggable, causing web compatibility issues. (Bug 1978673)
- Fixed a crash in the Web Developer Tools panel that could occur when inspecting pages with <iframe> elements. (Bug 1975277)
- Fixed minor visual issues across the user interface. (Bug 1974269 · Bug 1976031 · Bug 1974876 · Bug 1976701)
- Firefox failed to start with GTK+ built without Wayland support in uncommon setups. (Bug 1978620)
- Fixed an issue where clicking a pinned tab could steal focus from the content area, disrupting keyboard navigation. (Bug 1977005)
- Fixed a regression that caused issues on sites built with the Svelte framework. (Bug 1980081)
- Fixed an issue where cryptominers were not listed as blocked in Strict Tracking Protection. (Bug 1977066)
Mozilla released Firefox 141 last month, and with it came an AI-powered feature to organize tabs. Now, Firefox users are saying that the feature is causing high CPU usage.
Check the user reports in these posts on reddit (1, 2, and 3). So, why does the AI have high CPU usage? Instead of activating when a user right-clicks on tabs or tab groups, it probably runs in the background continuously. It's either that, or badly optimized code, which raises the question, how was this approved to the stable release?
How to disable AI-powered Smart tab grouping in Firefox
1. Open about:config and search for this: browser.tabs.groups.smart.enabled
2. Set the value to false.
3. Restart Firefox.
Firefox 142 introduces support for a flexible exception list in the Enhanced Tracking Protection (ETP) Strict mode, which should fix broken site features caused by tracker blocking. Exceptions are split into baseline (core functionality) and convenience (extra features), so you can opt for improved site compatibility without compromising key privacy protections.
9to5linux.com
you contribute to cut out the moaning we have no money syndrome?