mattmccutchen
commented
3 years ago My workaround for now is to just decline the "Open this site in your assigned container?" prompt every time I open a tab on the designated site (twitter.com in the original example) that I don't want to be in container X. That mostly works. Sometimes the prompt seems to cause single-sign-on and similar redirect flows to fail; my workaround for those cases is to perform the whole process in private browsing mode, in which the extension is inactive.
Of course, this approach doesn't work for the more general case described in #2117 where you want two containers X and Y, each of which is only allowed to open twitter.com.
The title is self explanatory. My suggestion is for the implementation of the possibility to restrict a container X to a specific site, for example, twitter.com, without having twitter.com be designated to that container only. That way, you would still be able to open Twitter in other containers or in a containerless tab, but the container X would be restricted to Twitter and you wouldn't have a container X tab open for any other sites. One way that I think that could be done would be by having, below the option ''limit (container) to designated sites'', a suboption that would say something like ''don't limit designated sites to container''. The option could be greyed out if the ''limit to designated sites'' option is left unchecked, since it would only make sense as an alternative if the container is limited to the sites.