- by Firefox user 12807353, a year agoRated 5 out of 5Probably one of the easiest and most secure ways to control privacy. It's like having multiple different browsers in private-mode without the ability for each to talk to each other. Each tab can be made to be isolated and self-contained. This can replace the need for "self-destructing" cookie addons, because once a tab is closed, all cookies/storage is also removed.
- by 098askjhgw, a year agoRated 5 out of 5It works very well!! In Automatic Mode, it seems that using the address bar to enter a different domain always creates another temporary container. I see the logic here -most typed urls from the address bar go to a different domain. All new blank tab address bar urls to go a different domain.
Two questions. Is there a way to match a typed address bar url domain with any existing temp container of the same domain and use that existing temp container being that their domains match?? I have Global Isolation Navigation and clicks set to Different from Tab Domain & Subdomain
Is automatic temporary containers per domain one of the intended use cases?? I used this with a clean ff install. It works great, but using the address bar leaves me with really way to many containers. This extension is great!Glad you like it! What triggers the new TCs when using the address bar is the Global Isolation. Automatic Mode creates new TCs primarily when opening new tabs.
If your goal is to have containers for specific domains, you might want to look into extensions managing permanent containers, like Multi-Account Containers (https://addons.mozilla.org/firefox/addon/multi-account-containers/). TC is meant to always create fresh temporary containers and not re-using existing containers. If you really think that should be a thing feel free to open an issue over on GitHub (https://github.com/stoically/temporary-containers/issues).
- by Firefox user 15119207, a year agoRated 4 out of 5Good enough sometimes, but often opens subdomains in new tabs even though I changed settings to do otherwise. Open in X container context menu option for Multi-Account Containers is broken, and I need to disable the addon everytime I want to add a new domain to a container.To reproduce the subdomains issue I'd need some steps to reproduce (ideally in an GitHub issue: https://github.com/stoically/temporary-containers/issues). Most of the time the issue comes from the fact that other domains are in-between when the redirect happens, which then causes the isolation.
"Open in New Container Tab" in combination with MAC isolation not working is expected behavior since the isolation will overwrite it (See: https://github.com/stoically/temporary-containers/issues/170). Alternatives to disabling the Add-on is globally toggling isolation, using the Alt+i shortcut (needs to be enabled in the advanced preferences under "Keyboard shortcuts") or the "crossed circle icon" in the toolbar popup (needs to be enabled in the general preferences).
- by The Voice Inside Your Head, a year agoRated 3 out of 5I use a local homemade written html file as a start/homepage [HP]. Each time I open the browser my HP appears but it isn't in any container. Make it so everything is in a container, including locally stored content.It's a Firefox API limitation which prevents automatically isolating file:// URLs, nothing I can do about it. (See: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/create)
- by Firefox user 15700431, a year agoRated 4 out of 5Well done! Really great work! For desktop. Thank you! Could you also make it available for FF on Android?
- by Hitmanigma, a year agoRated 5 out of 5Thanks you for the great extension! This and ublock are the two extensions that I can't live without. This is one of the most underrated extension for enhancing privacy out there.
- by User, a year agoRated 5 out of 5IT WORKS! THANK YOU!
=== Previous review ====
CAN'T INSTALL IT ON TOR BROWSER!
1. I have DISABLED permanent private browsing mode (browser.privatebrowsing.autostart = false).
2. I have INSTALLED Multi-Accounts Containers Add-on and it works FINE!
3. The problem is: I can't INSTALL your Add-on, not RUN it! Error message: "Installation aborted because the add-on appears to be corrupt". So, this is YOUR problem, not Tor's! Please, fix it!
https://discourse.mozilla.org/t/installation-aborted-because-the-add-on-appears-to-be-corrupt/43045You'd have to switch `extensions.allowPrivateBrowsingByDefault` to `false` in `about:config` too to make it work. Details: https://bugzilla.mozilla.org/show_bug.cgi?id=1600423
- by Dan, a year agoRated 5 out of 5A nicely done addon that comes closest to infocatcher’s private tab. I’ve set it to automatically delete cookies and history when the tab closes and that’s exactly what I wanted. A few more options would be nice, like hidng the address bar icon completely (had to use userChrome.css for that) but otherwise quite pleased.
- by Firefox user 15149992, a year agoRated 5 out of 5Awesome extension but doesn't work on Tor :((( Please fix!Thanks!
Tor Browser runs in permanent private browsing mode and the Firefox Container feature isn't available in Private Browsing - nothing I can fix, unfortunately. However, you could disable that in the Tor Browser settings under "History" and switch "extensions.allowPrivateBrowsingByDefault" to "false" in "about:config" to make it work, which isn't recommended.
- by jackinloadup, a year agoRated 5 out of 5Love this addon. This is fantastic not only for privacy/security for everyday use but also great for testing sites while doing development. It becomes really easy to be logged into all the different types of users in a website at the same time and see the interaction.
- by tel, a year agoRated 5 out of 5The add-on seems to cause some issues when trying to open a page in Private mode.
Steps to reproduce:
1. Enable the addon
2. Try to open a page in Private mode
3. Result - nothing happens
4. Expected results - a page to be loaded as usual
5. Disable the addon
6. Everything works as expected
It doesn't matter which page I am trying to load.
This behavior is since probably a a few weeks or so (not sure as private mode is usually not used). Nothing was change in the addon settings.
OS: Debian Testing (Bullseye)
FF: 68.2.0esr (64-bit)
Temporary Containers: v. 1.7Containers aren't supported in Private Windows. Before version 1.7 TC manually disabled itself in Private Windows, with version 1.7 it now relies on the Firefox Manifest "incognito: not_allowed" so it doesn't run at all in Private Windows. If you experience problems with pages loading in Private Windows while TC is active, I'd encourage you to report it to bugzilla.mozilla.org.
Might want to try in a fresh profile (about:profiles) as well, to make sure it isn't a custom configuration influencing the behavior, like also happened here: https://github.com/stoically/temporary-containers/issues/331