Reviews for Auto Containers
Auto Containers by Shajirr
Review by Firefox user 13156642
Rated 2 out of 5
by Firefox user 13156642, 3 months agoDoesn't work for purpose of following rules and sticking to well-organized containers; might as well disable and use private mode (which is not intent).
No matter what I try, I cannot get it to open new links from outside browser into my defined container.
Rules like
*, my_container
*.*, my_container
don't seem to matter. Instead, they always open in random tmp_ containers without any of my session/cookies.
No matter what I try, I cannot get it to open new links from outside browser into my defined container.
Rules like
*, my_container
*.*, my_container
don't seem to matter. Instead, they always open in random tmp_ containers without any of my session/cookies.
Developer response
posted 3 months agoShould be fixed now. You might need to trigger the rule sorting by adding any rule first.
Rules with only the wildcard as the primary domain part weren't treated as valid, so the addon was defaulting to assigning temp containers instead, but now they should work.
Rules with only the wildcard as the primary domain part weren't treated as valid, so the addon was defaulting to assigning temp containers instead, but now they should work.
4 reviews
- Rated 5 out of 5by Firefox user 14975781, 2 days agoThank you so much for this extension. I especially appreciate that it respects the rules even if they change the default behavior, like having a 'catch all' * filter that puts anything thats not filtered elsewhere into a 'default' container instead of a temp container is possible as well.
The only 'issue' i noticed is that on the preferences page trying to hit the save button always throws an error such as:
Invalid comma format on line (whatever): "*.android.com, Google Ecosystem". Format must be: Pattern, Name (no space before comma, space after comma)
This happens even if all the rules in the list were added through the GUI and no changes are made. Currently it's only 'editable' for me through the GUI.
Despite this, I love the extension! Let me know if there's anything I can do/any more information I can provide.Developer response
posted 2 days agoupdate - the issue should be fixed. There was a check to not allow spaces in container name, but since FF itself does allow them, I extended the check to allow any ascii characters/symbols + spaces. - Rated 5 out of 5by Firefox user 15196385, 2 months agoThis add-on was recommended by ChatGPT.
What I like about it: ① Newly visited sites are quarantined by default, ② Only frequently used sites can be saved as containers afterward.
The benefits: ① Lightbeam's graphs don't get messy, ② No more hassle with Firefox's bloated container tab list.
A minor annoyance is that using domain names or double-byte characters in container names causes errors.
I've been using both “Multi-Account Containers” and “Temporary Containers” until now, but Auto Containers alone seems sufficient.
For websites where “Sign in with Apple ID” opens in a new tab and then requires signing in via a pop-up window, you had to copy the URL from the pop-up window's address bar, paste it into the tab, navigate there, and then sign in with your Apple ID. - Rated 5 out of 5by badblocks, 6 months agoMuch simpler solution than using Containerise + Temporary Containers Plus. Especially like the 'Exclude Current Tab from Domain Isolation' for those tricky login flows that always waste my time.
In my quest to quickly create and manage containers as I browse, I would love a way to:
1. "Promote" a temporary container to a permanent one. If I forget to assign the container, allow me to promote the one I am already using, and suggest/edit the rule(s) before saving.
2. From the popup, edit the icon or color of any permanent containers I create, and have checkbox options to randomize each on by default.
3. Idealistic, for truly tricky sites: When in Exclude Current Tab mode, a way to let the user "start rule recording" and examine all domains browsed in this tab until rule recording is ended by the user. After, suggest a list of rules matching all seen domains and allow easily selecting one or more rules to add. Basically a way to add the problematic domains to a permanent container and avoid having to use Exclude Current Tab repeatedly for the same domains.
Great project thanks!
EDIT: And great update! Works perfectly!Developer response
posted 6 months agoShould all be possible to add.
n1 and n2 can be added to existing popup UI, while n3 would require something new.
One limitation with n1 idea is that the permanent container name should be a completely new container - there is no concept of "merging" containers, you can only rename them.
So even if you renamed the current temp container to the same name as an existing permanent container, you just end up with 2 separate containers with the same name with no real way to differentiate between them.