152 reviews

    === Previous review ====


    Dear Developer!

    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!

    You'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
  • A 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.

    Unfortunately there's no Firefox API available to hide the icon in the address bar, so userChrome.css is currently the only way to achieve that.
  • Awesome extension but doesn't work on Tor :((( Please fix!

    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.
  • Love 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.
  • The 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.7
    Containers 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
  • Respect!
  • Finally! A way to handle all the cookies, tracking, and other privacy bull pux! If you don't know how to setup containers, google or ask someone. Fortunately my really smart son feels the same about all the privacy issues and helps me! Your INTERNET provider collects ALL your data and sells it to multiple marketing companies, Homeland Security, & a plethora of other evil 3-letter .gov agencies! Just say NO to Google, Amazon, Facebook, etc monitoring ALL your browsing activity!
  • il refonctionnait et il vient juste de ne pas fonctioné
  • Terrific add-on, lets me essentially open mostly private tabs in a normal session. Would be nice if it had its own cookie blocking settings as well, all third party cookies being an example.
  • This is the way that containers should have been implemented natively. Thanks for this add-on and the effort that you put into this.
  • One of my must have. It makes browser so much private by isolating every websites inside their own temporary container. Just remember to not accept third party cookies. After leaving site all cookies are deleted, but you still keep your history. If you want to keep cookies from one site (eg. to keep logged in), just create persistent (normal) container for this one site and check to always open this one site in its own container. It still gonna be isolated, but cookies won't be deleted.
  • great
  • Cool work :-)
    I'd rather have some more control of temporary container names/colours, though: when you open several temporary containers at the same time, having them only called “tmp1”, “tmp2”, etc. may be a little confusing (it's possible to change it in the preferences, but that's not really user-friendly).
    I wish the toolbar button could display a small popup allowing to select the name, colour and icon for the container (pre-filled with the automatic settings). Would it be possible?

    *EDIT after the answer* I thought it as an option (I presumed that was in the aims of the toolbar popup when activated, but sadly not). I agree that it should not be the default behaviour.

    Since the Add-on is about temporary containers, having the option to change name/color/icon for already opened containers might lead to the impression that they're not really temporary but permanent instead - so I'll probably not implement such a feature.

    You can however long-click the new tab button, which reveals the container list and a "Manage Containers" button at the bottom, which is a quick-access to the container preferences where you could change its properties. Hope that helps.