multi-account-containers

the only thing i miss from containers is a shortcut to open a new tab using current container[0]. it would make usage a lot easier. [0] https://github.com/mozilla/multi-account-containers/issues/4...

I tried to move from Chrome's profiles to Firefox's container tabs. I prefer Chrome's take on it where sessions are shared across all tabs in a window rather than across similarly styled tabs in the same window. .. I just went to find the github issue for other people with a similar need[0] and found someone has posted a link to an extension called sticky containers. A new tab opens in the same container of the last one. It's actually pretty close to what I'm after.. https://addons.mozilla.org/en-US/firefox/addon/sticky-contai... [0] https://github.com/mozilla/multi-account-containers/issues/3...

I think the Facebook Container add-on does support this, though just for Facebook. There's an issue to add something similar to Multi-Account Containers, not sure what the status is on that: https://github.com/mozilla/multi-account-containers/issues/8...

It is many folks', and we appreciate the feedback. Hopefully things will get better soon: https://github.com/mozilla/multi-account-containers/issues/3...

It would be if I could restrict a container to a certain domain[1]. However, as it functions now, my containers are easily polluted. [1] https://github.com/mozilla/multi-account-containers/issues/8...

I am not sure if that'll be the case. The Multi Account Container (https://github.com/mozilla/multi-account-containers) seems like it's dead. No new commits since end of March and according to https://github.com/mozilla/multi-account-containers/issues/3..., it's only going to get bug fixes and maintenance patches. No new development. I have a feeling that they are relying on extension developers to add features/functionality.

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...

Or if you happen to run Firefox between multiple devices. It's been a pain maintaining a couple of instances' synced when it comes to containers (again, such a shame). There's an open issue [1], but no resolution yet as it seems. [1] https://github.com/mozilla/multi-account-containers/issues/3...

I believe the parent comment is referring to multi-account-containers [1], which is a general implementation. This Facebook extension is a reactionary Facebook-specific adaptation of that extension. But it is still useful for many users since it doesn't require any user interaction. I think multi-account-containers is more convenient than profiles since it provides a single interface to manage the containers and browser settings are shared, but I am actually using profiles on Firefox because the extension doesn't seem to support the "Never remember history" browser option. [1] https://github.com/mozilla/multi-account-containers and https://addons.mozilla.org/en-US/firefox/addon/multi-account...

You didn't allow every other Add-on to access the API, but explicitly only the Add-ons with the "contextualIdentities" permission ("Container feature"). Which is the reason the "management" permission ("Monitor extension usage") was needed in the first place - to check if the Add-ons accessing the API have that permission. Also, the API doesn't give external Add-ons access to the permissions you gave the Multi-Account Containers Add-on, but instead only a really specific amount of information; which is whether a specific domain is assigned to a container (you can read about it here https://github.com/mozilla/multi-account-containers/wiki/API). Now, why "automatically" for Add-ons that have the "contextualIdentities" permission? It's simple, if you grant an Add-on that permission, you already gave your consent that the Add-on can access th

I’ve had it installed before and received the prompt “to install the update of this extension please accept the new telemetry conditions.” I don’t claim every user sees it (maybe I’m a/b tested?). I’ve rejected it, and checking the repo wouldn’t help for that. The new requested permission, different from the ones previously accepted by me is, if I remember: "Monitor extension usage and manage themes" What's that if not a new telemetry? In a privacy-oriented extension! It's explained here: https://github.com/mozilla/multi-account-containers/wiki/Per... ""Monitor extension usage and manage themes": Required to provide interoperability with other container Add-ons by checking if they have the required permissions." How about not being required? Older versions really didn't require. Knowing the management (see "Looking Glass"), even if the ex