Downloading a file from Google Drive. Downloading redirects me through a set of intermediate sites that I can't navigate to and add to container because they're automatic redirects. I have my "Google" container so that its "Limited to designated sites". Because I can't whitelist these sites, it directs me outside my container and gets me stuck in a redirect loop.
Either ability to add sites to a container by typing in a URL or some other way that I can limit google cookies to only google sites and handle redirect from those sites easily
I think I'm having this problem with some of my banking accounts too, basically anything where a log in redirects me to a different url and I can't access that URL because its an automatic redirect. I want specific sites to run only in their container and not have access to my other browsing, or not let cookies from my other browsing exist on specific sites. An easy solution in my mind is to add a field in the "Manage site list" option so that you can type in urls there instead of having to actually navigate to them but open to suggestions.
I would really prefer to have the "Limit to designated sites" checked because I don't want to have to actively close and open containers when I want them
Love this idea though, really cool product. Definitely very happy that this exists.
This could easily be solved by having a + button and a text field in the "manage site list" submenu for each container. I can't log in to Google/YouTube because of this and have to manually fiddle with turning off the limit option, trying to log in, adding the subdomain then reenabling the limit option. You should not have to navigate to a domain to add it to a container, typing in the domain name should be possible. Why this wasn't one of the very first implemented features in the first place is beyond me.
As an additional piece of the underlying requested feature, we should be able to do a certain amount of pattern matching.
So *.google.com would get all Google subdomains, while !oauth.google.com would exclude the OAuth subdomain so it doesn't break other containers (I don't know if that's the subdomain for it, but you get the idea).
I would personally find URL pattern matching very useful. https://bitbucket.org/MyCompany needs to open in a MyCompany container, while https://bitbucket.org/SomeOrg needs to open in another container.
Hello,
I was looking for a way to add or edit site listed inside Multi-Account Containers.
It would be very useful to add and edit site directly inside the Multi-Account Containers add-on using glob pattern as suggested by @ShaunaGordon and/or url matching patterns as suggested by @ShonFrazier without needing to visit each site to add them to a specific container.
As a workaround, it is not perfect but it's working, I'm using Containerise add-on on which I can add and affect directly site to specific container using "special" glob patterns (seems to not support negate pattern) and then when a targeted site is visited, add it to the container asociated site list in Multi-Account Containers using Always open this in a Container (required if you are using Temporary Containers to avoid conflict between Multi-Account Containers and Temporary Containers). But do not enable Limit to Designated Site in Multi-Account Containers because if Containerise is matching a site not listed in Multi-Account Containers for as example a container named Test this will generate an infinite loop with Containerise opening tab inside container Test and Multi-Account Containers closing this tab for container Test and so on ... you need to click on close tab as fast as possible :)
I hope such a feature could be added to Multi-Account Containers.
Kind Regards
Most helpful comment
This could easily be solved by having a + button and a text field in the "manage site list" submenu for each container. I can't log in to Google/YouTube because of this and have to manually fiddle with turning off the limit option, trying to log in, adding the subdomain then reenabling the limit option. You should not have to navigate to a domain to add it to a container, typing in the domain name should be possible. Why this wasn't one of the very first implemented features in the first place is beyond me.