multi-account-containers

Related issue: https://github.com/mozilla/multi-account-containers/issues/2...

There's no obvious reason to grant the nativeMessaging permission during extension installation for an optional feature, nativeMessaging can be declared as an optional permission since Firefox 87 [1], and Firefox Multi-Account Containers 8.0.2 only supports Firefox 91 or newer. There could be a bug related to declaring nativeMessaging as an optional permission, though that is not mentioned in the pull request [2], so this was probably an oversight. EDIT: the minimum supported version was bumped to Firefox 91 in a subsequent PR apparently not for technical reasons, but just to follow guidelines [3], and then they forgot to reevaluate the need for the new default permission before a release. [1] https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web... [2] https://github.com/mozilla/multi-account-containers/pull/215... [3] https://git

Should be possible, but not sure if the code calls it unconditionally. You can also take the old version of the source code and publish it yourself. Though possibly you can also just download and install that directly? https://github.com/mozilla/multi-account-containers/releases...

I wish they fixed the long standing, annoying sync bug that makes Firefox download 7000+ containers every once in a while. Some of us hosed our sync accounts in one way or another (through the container duplication bug in m-a-c itself [1] or the temporary containers extension [2]) and it's impossible to recover - once you reach the storage quota on the sync server, the sync server refuses all write operations and delete call apparently counts as a write. [1] https://github.com/mozilla/multi-account-containers/issues/1... [2] https://github.com/stoically/temporary-containers/issues/371

Tab Containers are a nice feature, but aren't quite there yet. For example, history is currently not isolated per container: https://github.com/mozilla/multi-account-containers/issues/1... https://bugzilla.mozilla.org/show_bug.cgi?id=1283320 Multiple browser profiles also let me have one profile for work, another one for personal stuff, and yet another one only with stuff like vue/react/svelte dev tools and remote debugging enabled, and _then_ decide which one to open at any given time. This instead of opening every container at once, or something like selectively opening a bunch of bookmarks manually into a specific container (I use buku to manage and sync my bookmarks too, so no tab container support there).

Hey there! I'm one of the devs on this project. We made some progress last year on per-container proxy support. Follow this issue for (hopefully soon) progress here: https://github.com/mozilla/multi-account-containers/pull/190...

Strong agree on multi account containers. Keep in mind though if you disable them they drop all settings, unlike every other add-on ... ever. Bug is three years old but maybe we can push it over the top: https://github.com/mozilla/multi-account-containers/issues/1...

I switched to FF on Windows 10 as my daily driver a year and a half ago in order to adopt a multi-account container workflow. MACs aren't perfect [1] and overall I definitely sense that FF is not as power-efficient as Chrome, especially when in a Meet call, but overall I'm very happy with it and the power thing is not a huge issue if I'm sitting wired in all day anyway. [1]: My criticisms: https://github.com/mozilla/multi-account-containers/issues/1...

I agree. As someone who works with numerous customer environments this extension is critical for my productivity. Having a different profile (ie Chrome style) is nowhere close. If the container re-ordering patch[0] would be implemented it would be perfect, but it seems to be stuck in limbo. If Brave implemented this and did it right (with sorting & reordering) I would consider switching. [0] https://github.com/mozilla/multi-account-containers/pull/160...