- Rated 2 out of 5by tsap, 24 days agoloving the add-on but hatin this annoying question screen every time i'am opening site in other than saved container
"Open this site in your assigned Container?"
please remove it or make option to turn it off.
- Rated 2 out of 5by VS, 2 months ago4 Days Ago I Installed It. And I Added Facebook And Instagram In Social Media Container. Also I Add Gmail, Google Drive, Youtube In Google Container. Today On 4th Day Of Usage, It Automatically Logs Out From All Websites Like From Facebook, Gmail, Instagram. It Should Keep Logigng Me In On All Logged In Sites. Thats Why Rate It 2 Stars Only. Fix It Please.
- Rated 2 out of 5by Firefox user 15993249, 4 months agoWorks well untill you change computer and set up a new browser. The containers are synced in random order an there is no way to sort them in "Open new tab" menu or in about:preferences#containers tab. There is sorting when clicking on a badge but it doesnt affect order in new tab button. So if you want to have same sorting in 3 different browsers you have to delete everything and create containers one by one constantly syncing and checking all devices. Horrible UX.
- Rated 2 out of 5by user, 7 months agoI have Firefox 109.0.1.
Firefox Multi-Account Containers 8.1.2 can't open links outside of any container from the personal container if user made 2 confirmations... Links will open inside the personal container instead. It's not clear if there are any hidden settings around this. I don't think that manual requests from the context menu should follow the general rule, they should be given priority. Left clicks and the address bar must obey the rules, but right clicks must take precedence over the rules.
Firefox Multi-Account Containers 8.1.2 will ask for confirmation twice when assigned and then when opening any website.
By default, Firefox Multi-Account Containers 8.1.2 doesn't have even the largest banks...
By default, Firefox Multi-Account Containers 8.1.2 doesn't have even the largest marketplaces and shops. Users have to add shops manually... Definitely not suitable for smaller shops.
It's not clear how to create more than 4 containers or rename the standard ones with Firefox Multi-Account Containers 8.1.2...
It's not clear how to clear some or all containers with Firefox Multi-Account Containers 8.1.2... Users don't have visible options.
- Rated 2 out of 5by Ayush Patel, 8 months agoHi Team,
My Container extension is not working. It is really disappointing. I recently organized my work according to containers tabs and now it is not even loading. Please look into it on priority.
Let me know when its fixed.
- Rated 2 out of 5by dluc, 9 months agoIt must be integrated with bookmarks to be really useful. Sometimes it's not about about the domain but about the starting page. E.g. I want to use a "Google" container when starting from page X, and a "Personal" container when starting from page Y - regardless of domain settings, actually overriding those.
- Rated 2 out of 5by Firefox user 17404988, 9 months agonumerous openid/openid connect workflows get broken by this, cant use google login safely due to the intervention it has when using different google accounts in different containers
- Rated 2 out of 5by Henrik, 10 months agoI just want something simmilar to Tab Groups in Chrome. I tried 4 different Add-Ons and this is the best so far. But even this doesn't have the option of hiding groups. There are tons of features, but the basics are missing. Really sad.
- Rated 2 out of 5by firedoge, a year agoPretty handy. But the icon in the URL bar is pretty annoying, as these cant be removed. It is not nessecary, but when tiling the FF window in half the URL bar is nearly completely gone, which is not nice.
- Rated 2 out of 5by Shajirr, a year agoI've found Containerise to be a way better addon than this.
MAC for me takes like 10 seconds to load the menu, Containerise opens instantly.
Adding a website to a particular container is quite an annoying process, since you need to scroll the container list, and there can be dozens of containers there if you use Temp Containers addon.
Meanwhile, in Containerise adding it is very easy - you can even edit the config in form of text directly, you can also import/export the config in the same way, as plain text.
- Rated 2 out of 5by Hej, a year agoI'm going to lower my rating even though I still think this add-on is crucial and fantastic. But the fact that you still, after many years, haven't added the option to manually add a url to always open in a certain container is ridiculous. You should know how chaotic and irratic the devs of Google and Microsoft are today using 20 different domains just to be able to sign in somewhere. It's like they all suffer from DID. It's a hassle to use containers because of this, since you so often are thrown out of the container. Fix it!
- Rated 2 out of 5by Firefox user 17558208, a year agoDoes not work reliably for me at all. After a Firefox restart, tabs will randomly become unassigned from their containers, and occasionally the entire contents of a container will disappear. Then I am left with trying to sort out the mess of tabs left over, attempting to put them back inside containers. Happens on multiple machines and multiple user accounts, perhaps some incompatibility with uBlock Origin? Or this addon is just not mature enough yet.
- Rated 2 out of 5by Rômmulo Pëixoto, a year agoMy system crashed for lack of memory, and I had to force Firefox to restart. With this procedure, one of the containers I created, lost all the history of the tabs open in it!
That way it got worse than before, when it was possible to recover a lost session with all previously opened tabs, directly on the side panel of the browser.
But the worst, is that each container when opened, recharges at once all the tabs saved in it, so only worsens for those who want to optimize the use of memory.
Brazilian Pt: Meu sistema travou por falta de memória, e eu precisei forçar o Firefox a reiniciar. Com esse procedimento, um dos conteiners que criei, perdeu todo o histórico das guias abertas nele!
Dessa forma ficou pior do que antes, em que era possível recuperar uma sessão perdida com todas as abas abertas anteriormente, diretamente no painel lateral do navegador.
Porém o pior mesmo, é que cada container ao ser aberto, recarrega de uma só vez todas as abas salvas nele, então só piora para quem deseja otimizar o uso da memória.
- Rated 2 out of 5by Jose, a year agoI really like the idea, but I have a major problem with the way it implemented. Whenever I close the window and open it again, tabs that were previously in one container, reset to the default (non-container?)... if the window is closed and has contained tabs on it, once it's opened, it should contain the same containers and non-container tabs...
- Rated 2 out of 5by Nathan Never, a year agoSarebbe un'ottima estensione, ma funziona ancora maluccio e da alcuni problemi. Un problema è che se ho eBay in un contenitore e Paypal in un altro, e li ho impostati che si aprono automaticamente in quei contenitori, non c'è modo di pagare. Altro problema: avevo eliminato un contenitore in quanto mi ero accorto che, come ci avevo impostato MozillaVPN funzionava male (non c'era trasmissione su quel server). Quando sono andato a richreare un nuovo contenitore alcuni siti si aprivano e si richiudeva subito la scheda, per riaprirsi di nuovo e richiudersi e cosi via. Fatto alcuni tentativi, riavviato F, ed alla fine ho disabilitato l'Addon Firefox Multi-Account Containers. Tutto bene, dopo il sito si riapriva perfettamente ma 😱 ... quando sono andato a riattivare l'addon era tornato alle impostazioni di fabbrica con solo 4 contenitori, tutti gli altri che avevo fatto, tutto il lavoro ed il tempo che ci avevo dedicato, puff, scomparsi. Cosa ancor più snervante: il famoso segnalibro si riapre nel contenitore che gli avevo assegnato ma non compare nella lista siti nel contenitore stesso. E se ce lo aggiungo me lo apre due volte. Ma porc....
Ho letto nelle recensioni di altri problemi, tipo quando si fa un aggiornamento di firefox.
Ora, mi spiace, ma rimuovo l'Adon. Sarebbe stupenda come estensione ma c'è ancora tanto, ma tanto, da fare.
- Rated 2 out of 5by DankAddoner, a year ago"Open in container" settings doesn't work properly for me. If I select "cancel" option for it, it won't remember and will bother me every single time with the "open in container" prompt.
- Rated 2 out of 5by Amazing Mr. X, a year agoThis has a lot of potential, but it's not quite ready for prime time. There's a few specific problems here:
Firstly, add-ons can't communicate with the content of containers. This breaks functionality in most add-ons in really weird and unexpected ways. It'd be nice if we could whitelist add-ons to have access to relevant containers, but most users would probably want all of their add-ons to have full access to all of their containers by default and wouldn't expect them to be functionally blocked as they are.
Secondly, containers don't nicely handle redirects. A lot of sites, especially corporate ones, will redirect through several different domains and subdomains when performing the login process. Containers set to "Limit to Designated Sites" won't operate correctly with these redirects as the redirect pages are not true web pages and don't allow you to sit on them long enough to click the address bar button to always open them in the specified container. This cannot currently be remedied by having foreknowledge of the complete list of redirect sites, as the "Limit to Designated Sites" list cannot be manually edited or appended outside of the limited address bar button method.
Thirdly, The VPN integration isn't particularly secure in premise. Being a per-container opt-in means that entities snooping on the line will immediately see that there's something suspiciously different in the data packets coming from your protected containers compared to the rest of your typical https encrypted traffic. This makes isolating these packets, on the fly, infuriatingly trivial. Making this a per-container opt-out would all but eliminate this problem, as attackers would have to have foreknowledge of the originating container to do this effectively in all circumstances. It'd also be great to see connection protocol options ( OpenVPN, WireGuard, etc. ) as well as other VPN provider options as that'd make it that much harder to try and figure out what's going on in the encrypted container traffic and would better protect Mozilla VPN itself. Right now it's technically more secure to not use the VPN feature at all.
I think the basic idea here is really excellent, but these problems really do drag it down. Something made and maintained by Mozilla shouldn't have this many problems. I still think this is potentially useful to certain technical professionals trying to isolate their sensitive internal sites from other web apps, but the average user is going to have too many headaches to be able to use this effectively.
If you know what you're doing, keep the above points in-mind and go ahead and give it a try.
Anyone else? Hope Mozilla addresses some of these issues in a future release. I'll update my review if they do.