It looks like Chrome is going to add post-quantum key exchange X25519Kyber768 to secure TLS connections, see https://chromestatus.com/feature/5257822742249472

As much as I hate Chrome, I'd like to see such a feature in Firefox too. Any idea if there's a technical discussion/proposal somewhere?

Opera's new 'Tab Islands' feature is very cool and I've wished for such a feature in FF.

Briefly, "When opening new tabs from a webpage, those tabs are automatically grouped together into an island."

https://blogs.opera.com/news/2023/06/opera-tab-islands/

I happen to be one of those bozo users with hundreds of tabs open all the time and I'm always interested in any feature, addon, plugin, whatever that would make it easier to keep my tabs organized.

Anyone know of such a feature in FF?

Is there a way to see how much memory each Firefox Add-On uses? I've tried to look into "about:processes", and "about:memory". The first one tells you the total amount of memory used by the Add-Ons, and the latter gives you a 30,000 page long report that I don't know how to make heads or tails of. I KNOW my Add-Ons are eating up a lot of memory. I want to know WHICH ones are eating up the most so I can know which ones I should maybe shut down. Ideally, I wouldn't shut any down because they are all geared toward productivity. But maybe I can prioritize some over others.

Is there an easy way to view this information? Something akin to the Chrome web browser?

#firefox

In the latest Firefox version(116.0.2 (64-bit)) the button "List all tabs" won't show any tabs unless I close like half of them, then it works again if I open new random tabs. Currently 246 open tabs.

Any other way to fix this? I don't really wanna close those tabs.

The way I know this is that I tested in a sandbox with the same profile to try to find the problem.

EDIT 14/Aug/2023: So I just found out the issue was some tabs that had a " --" at the end of the title probably caused by some addon made this issue happen. It probably isn't really a - but I don't know what character is that.

All you have to do is just copy the url, open a new tab, paste the url and go. Close the previous tab with " --" at the end.
Just make sure you are not opening a new tab with CTRL+(clicking the + icon) from the "broken" tab with the " --".

Example.

Hope this helps someone else.

In the coming months Mozilla will launch support for an open ecosystem of extensions on Firefox for Android on addons.mozilla.org (AMO). We’ll announce a definite launch date in early September, but it’s safe to expect a roll-out before the year’s end.

I currently have a puny 380 tabs open that consume 42GB RAM on my MBP '21 Max whatever (with 64GB total, shared with the GPU).

I have gone through most troubleshooting and it's clear that the unload mechanism isn't achieving it's goal (I mean, aside from an absolutely psycho amount of tabs I am hell-bent on having to "come back to later"). The reason that these tabs are open and have been loaded is that I've been transferring my other browser tabs over and setting up my Containers & Sidebar Panels, so each tab would have to be open within the last week.

Question: Most of resources I've found online lead me to believe that all I need is to modify browser.low_commit_space_threshold_mb. But it's nowhere to be found. about:config on MacOS is just returning an empty value and offers me to set it. Dare I? Would it actually work?

And yes, the browser.tabs.unloadOnLowMemory is set to true and browser.tabs.min_inactive_duration_before_unload is a default 600000 (which is in ms IIRC, so it's 10 minutes)

My main issue is that even manually triggering the Unload from about:unloads doesn't help the situation, and it can't be that all of the tabs are using WebRTC or are somehow considered to be active? Can it be a side-effect of Sidebery extension? Surely not? Many of the tabs list "Last Accessed" datetime between 3-9 days ago and still have the Base Weight of 0, so that part probably works, but Firefix decides not to unload them?

--
Random thought: It would really help if people wouldn't need to chase this. I assume that the way that MacOS handles RAM with it's swap and whole "memory pressure" is probably isn't the most simple thing to work around but unless I can fix this it'll be very difficult to consistently use, and I can imagine people less inclined to figure things out be easily turned off. And yes, I didn't use to have this problem with the other browser with just as mental number of tabs.

Day 9 of (finally) moving away from Chrome after Web Integrity API proposal is going swimmingly, as you can see.

Edits: formatting, added more details of troubleshooting

It appears to add fewer than other browsers, but I'm not quite sure why it adds "?channel=fenc&client=firefox-b-1-d" to searches when only the q/query parameter is needed for them to work.

someone in the mood to confirm a bug with me? I think this is new. Seeing this with F115 (on linux) on a clean, new profile. The code didn't change.

I used to be able to listen to a big audio file in a streaming manner when loaded from goldfire/howler.js library.

The new behaviour is: firefox will download the whole file before starting to play.

Example: (25MB bytes down will occur) https://jsfiddle.net/ugnt03jo/1/ -> click Run in upper left to render html

• if you have traffic stats on your system you'll see bytes trickling in the moment you render the html - not when you click the Play button. This is acknowledged in the devtools network-tab after it is fetched in full
• until fetched in full, the Play button will not stream the audio file

#firefox

Is there a Keyboard Shortcut to put the focus on Firefox's Sidebar?

I use the Add-On "Bookmark search plus 2" which is really awesome. When I activate it's Keyboard Shortcut (Ctrl + Q), the Sidebar opens, but I have to use my mouse to click on the Sidebar to grant it focus. I looked around online and haven't found anything. If anyone knows of a way, a Keyboard Shortcut, a tool or another Add-On perhaps, please let me know! Cheers!

#firefox

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

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.

A comprehensive mapping of old subreddits to new communities.

This might be a little late for this year, but we can definitely start playing with some ideas for next year (or maybe we can run the logo next month).

Wouldn't it be cool to rebrand the magazine logo here in a Firefox+Pride themed way? Your logo should be square-ish so that it fits in the Kbin sidebar.

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 🧵