Auto Containers by Shajirr

This addon aims to provide automatic domain isolation using Firefox containers, to reduce cross-site data tracking.

Temporary containers

By default, each new domain will be opened in a temporary self-destructing container, that will be auto-deleted after all tabs using it are closed, along with all of their saved data. This process is fully automated.

Permanent containers

For sites that you use regularly, you can define rules to open them in permanent containers instead.
This will allow you to keep their data (like active logins or preferences), but still prevent other sites from accessing it.

Rules for permanent containers can be added either from the addon's Options page, or from a popup opened by clicking the addon icon on the toolbar, which also has most likely suggestions which you can select.
Popup will also list all the rules associated with the current tab's container, so you can quickly edit or delete any of them. Rules support wildcards.

Rules order does matter, they will be checked in the same order as you see them, although they are also auto-sorted to prevent more generic rules blocking more specific ones, so the user shouldn't have to worry about this in most cases.

Addon is made with the ease of use in mind, to automate container management as much as possible.

Override rules

In case some data must be transferred between domains, override rules is one of the ways that can be used to achieve that (another one is Exclusions).
Example - you have Youtube isolated in a YT container, but when you attempt to log in, it will navigate to accounts.google.com, tab will get replaced due to needing a new container for isolation, and your login process will fail. Solution - add:
'accounts.google.com, YT'
to override rules.
This way if the addon encounters 'accounts.google.com' URL while your tab is in YT container, override rule takes priority, tab stays in YT container, and your login succeeds.
Meanwhile, if you just open 'accounts.google.com' in a new tab, it will still get isolated in a temp container (or into whatever container was assigned to it in regular rules)

In case there are many different domains you need to override, and you don't know all of them, you can use the domain recording feature.
First, open your webpage that matches a default rule.
Second, use "Exclude tab from domain isolation" option from the page context menu. This prevents container change / tab replacement on domain change.
Next, go to Options, and start domain tracking by pressing "Start Tracking" button.
Then, perform whatever login / payment or other process that needed to go through multiple domains. After its done, stop the tracker in Options page.
It will give you a list of all the domains you went through - copy it somewhere, and then add override rules based on the domains recorded.
Finally, use "Remove tab from exclusions" page context menu option to restore domain isolation for the tab (or just close it)

Usage instructions

• Container style section in the popup menu is collapsible, in case you don't need it
• When adding rules, container color / icon selection applies only to new containers, color / icon of already existing containers won't be overwritten
• If you want to change icon / color of an existing container, then open / switch to a tab that is in that container, and after selecting icon / color in the popup menu, click "Apply to current container" button.
• last color in the color selection grid is a theme accent color, it depends on which FF theme you're using
• If you want to convert the currently opened container to a permanent one, in case you don't want to lose the data from your temp container - check the checkbox "Convert current temp container" when adding a rule. That will rename the current temp container to the same name that you added in the rule, and you will keep all the the data from it. Note that this works only for new containers, not if you select an existing container in the rule, as container merging is not possible by design.
• In the Options page you can set the default icon / color for the temporary containers, or to have each assigned at random

Exclusions

There are cases where maintaining the same container even when navigating to a different domain is required, for example, when the login process is handled on a different domain, or when making payments and you're being redirected through multiple payment processor / bank pages. For such cases you can temporarily exclude the tab from domain isolation, to keep the tab in the same container.
Right click anywhere on the page, select "Auto Containers" -> "Exclude tab from domain isolation".
If the tab is added to exclusions list, the addon badge on the toolbar should show "EX".
To remove the tab from exclusion list and restore domain isolation, select "Remove tab from exclusions" in the same menu.
Note that the tab excluded from domain isolation will pass this status to any tabs opened from it (child tabs) - this is useful if the process you need to complete opens the next page as a new tab.

Reserved container names / special rules

You can activate special rules by using the specific reserved container names.
Warning - these options can lead to breaking domain isolation.
* #Default - will always open the matched address in a default Firefox container, which is the same as no container
* #Ignore - the addon does nothing with a matched address. By default Firefox will assign the same container (or no container) as the tab its opened from.

Compatibility

This addon is incompatible with other addons that can automatically assign containers to tabs, as they will be interfering with each other, some examples of which include:

• Firefox Multi-Account Containers
• Temporary Containers
• Containerise
• Facebook / Amazon / etc. container - any site-specific container addons

Known issues / bugs

Suggested ideas / Plans

• Add the ability to open a link in a specific container, along with an automatic temp exclusion rule, allowing opened URL to stay in selected container.

Permissions

• Display notifications to you - self-explanatory
• Access recently closed tabs - needed for sessions API - allows writing data into tab objects and retrieving it. This data survives session restore, which is used to store individual tab history.
• Access browser tabs - needed for access to tab titles and URLs, which is required for almost all core functionality
• Access browser activity during navigation - used to record tab history, to record domain changes for Domain Hop Tracker, and to call the main function that handles container changes on navigation