Sort of tangential, but as an account-containers user, have you found a decent way to achieve making the current container "sticky", so that new tabs opened in a given window go directly to that container?

I currently use Chrome's account profiles for this, so I have a desktop where my work profile lives and a desktop where my personal profile lives, and this makes links followed from other applications Just Work so long as I'm on the right desktop for them. I could probably get used to a slightly more awkward workflow, and the history being annoyingly shared between them, but...

EDIT: ah, well, I found the relevant github issue. Looks like there's years of arguing yet to go! https://github.com/mozilla/multi-account-containers/issues/3...

Firefox can already run multiple profiles simultaneously (like you do with chrome) http://kb.mozillazine.org/Command_line_arguments .

The problem is not having just one instance open all the links. It seems it might be possible to hack around that by writing your own url handler for your os, then dispatching to the correct instance. (https://superuser.com/questions/119014/how-to-remotely-open-...)

I did try that out, when I was seeing if I could stand switching after multiprocess stuff landed. It's closer to the fairly-polished Chrome experience if you use about:profiles, rather than messing around with custom command lines.

But, as you say, the problem with that is that it doesn't handle opening links correctly.

I could see if I could write a URL handler that queries the window manager to find the last Firefox window that had focus on the current desktop (probably possible, but I'm unfamiliar with that domain)... or I could view Firefox not supporting this natively as a sign that it doesn't think my use case is very important, and stick with a browser that works without jumping through hoops.

It's not that I'm averse to putting some work in, per se -- I'm now in the middle of poking at writing a Firefox add-on to see if I can fix my complaints about insufficiently sticky containers -- it's just that writing my own OS url handler is a bit too hacky for my tastes.

I have been using the Conex extension. It opens the new tab in the same container as the currently active tab and you can enable the preference to make it so that it asks you which container you want to use before opening an external link.

https://addons.mozilla.org/en-US/firefox/addon/conex/

I've written my own now, which just approximates the Chrome behavior. (I looked at Conex after you linked it, and it didn't quite do what I felt was right.)

https://github.com/kemayo/firefox-sticky-containers

I'm currently seeing whether #webextensions on irc.mozilla.org feels like ripping it to shreds, but I'll put it up on AMO after that's done.

Okay! Here it is: https://addons.mozilla.org/en-US/firefox/addon/sticky-contai...

I did the same with Chrome account profiles, and I just searched for this on Firefox. The closest you get to it is ctrl/cmd + "+" (new tab button) which will open a new tab with current container.

No keyboard shortcuts to speak of.

uMatrix is a good replacement for Ghostery.

https://addons.mozilla.org/en-US/firefox/addon/umatrix/

Firefox has built-in tracking protection that can be enabled in non-private windows too.

Nice! This was my number one issue with Firefox as well. 400% cpu usage with about 40 tabs compared to safari was getting to be too much.

Yes I'm one of "those" people. I hoard tabs like they're going out of style.

What incantation do you do to make your cpu go to 400%?

Sorry, the main process goes to 140%, and about 5 more other firefox processes start chewing up 80% cpu each. I just added them altogether.

I have seen it spike to 400% a few times in activity monitor.

As to what I'm doing, open up say lobsters, click on all the tabs that look interesting, forget them for a day, repeat. End of the week have a look see at things.

Mac shows CPU usage as 100% per core. Means he has a quad-core or dual-core w/ hyperthreading.

Linux does the same thing too. I wonder whether this is a POSIX thing, or if it's just a rather common UNIX thing.

Could you please report back with your findings? I'm also terribly interested in this as well.

Just updated!

For me the problem was only when firefox was running in retina mode. Going into Applications > Firefox > Right Click Get Info > Check "Open in Low Resolution"

The problem was fixed, but all the text looks bad now.

That's interesting. That fix seems unreasonable for me considering I already have difficulty reading on screens. But that's at least a point to look for later on in the release notes.

Most likely related: https://bugzilla.mozilla.org/show_bug.cgi?id=1404042