erosman
commented
2 years ago It appears that when a container tab is opened by another process and that site is not listed, and siteIsolation is true, addon attempts to remove the tab and re-open it in the default container which creates an endless loop with the other addon.
I would suggest that siteIsolation should only come into effect:
- if there are listed sites
- if the tab is navigating from a LISTED site in a container to an UNLISTED site
the-rhetorician
If "Firefox Multi-Account Containers" is installed and "Limit to designated sites" is enabled (without any sites listed, there will be a conflict with another container addon (FoxyTab).
I am not sure where the exact conflict is as the addons behaviours are not the same. I look forward to feedback and will work on eliminating the issue.
Actual behavior
example.comin Personal container & "Limit to designated sites" disabledexample.comexample.comin a new Personal container (its function ends there)Expected behavior
Once a tab is opened in a container, there shouldn't be a need for re-navigating it
Notes
Maybe there is a need to limit access when there are more than one addon is handling an API, similar to Network Settings addons :thinking: