It works, but if you try clicking a link on a facebook related page with facebook containers on, it bugs.

Interesting idea but it's buggy right now. It opens double tabs when used with "Auto Tab Discard" add-on.

Does exactly what I wanted when opening new tabs, though it does it after you put in an address in the default container.

Unfortunately, it doesn't allow me to easily open a new window; when you attempt to open a new window from a container tab (Alt/Command-N or File->New Window), the new window immediately closes. You can still open a new window via opening a new tab and dragging it off of the original window, but this is very inconvenient in an multi-workspace environment like KDE, where I often simply want to open a new Firefox window in the current workspace. Moving to the original workspace, dragging a tab out to make a new window, then bringing the window to the workspace I want it is really annoying to do when I simply just want a new Firefox window now.

For my use, this issue makes the add-on basically unusable. Hopefully, this issue can be fixed, or this feature can be part of the base Containers system.

A good interim workaround for bulk tab imports until they get open in set container/open in original properly sorted.

It reopens the tab when the tab is clicked, in the container that was active before the tab was imported.

Drawbacks: Not working properly with tree tabs.
The tab order is changed, tabs are re-ordered into the order they are activated, and tree structure is lost. (This happens using tree tabs addon, may be caused by it??? - Might this be because the old tab is closed before the new tab is opened?)

Brilliant for bookmarks, onetab etc until open in origina container gets sorted.

This add-on makes dealing with containers much easier, but it requires a lot of polishing.

I just found three bugs:

1) Customisation mode cannot be activated, because the add-on tries to "contain" it, what causes it to break (the add-on should check if it's the customisation tab that's being opened and avoid trying to "contain" it). Other built-in Pages work fine (about:config, about:preferences and so on). The bug only shows when the customisation is activated on a window with containers.

2) Control+N or File -> New Window opens a new container tab, instead of a new window! Once again, the bug only shows up when the commands are used on a window with containers. When done on a window without ANY containers, a new window is normally created (it doesn't matter if the active tab is "uncontained"). If, for instance, no window is uncontained, the is no way to create new windows (dragging a tab out of its window, luckily, still work, so it's possible to "produce" new "uncontained" windows by creating an empty tab, which will be contained, drag it out to create a new window, then switch the container of that new tab with Switch Container Plus, which is currently the only add-on able to change containers of empty tabs). Too much trouble just to create a window, but still possible.

3) When recovering from a crash, ALL tabs on ALL windows are "contained" (kind of randomly, depending on the first contained tab Firefox restores (it doesn't have to load it, just its presence in any window is enough to "contaminate" all other tabs). It's, in a word, disastrous, as all tabs change their containers (even uncontained ones), messing with logged in accounts, changing site preferences and whatnot.

Currently, this add-on is unusable (yes, it works fine enough while everything is running smooth, but then it may mess up everything in the event of a crash or restart).