4 ms·
I tried using containers for a while, and found them to be severely lacking. One example: You can't edit a container's site list, you can only add the currentl
by boring_twenties 3y ago
I tried using containers for a while, and found them to be severely lacking.
One example: You can't edit a container's site list, you can only add the currently loaded FQDN to it. So, you can't for example assign *.google.com to your Google container, you can only add each individual subdomain, and only after loading it.
Worse, if a host you want to add is part of a redirect chain, there seems to be no way to add it at all. For example, mail.google.com redirects you to accounts.google.com which quickly redirects you back to mail.google.com. There is no way to get accounts.google.com added to the list. As a result of this, the "Limit to designated sites only" feature is completely unusable. (And the only reason these problems exists is because Mozilla in its infinite wisdom has decided that an Add button and a text input in the sites list would be too much for us lowly users.)
Another common annoyance I had was the inability to clear cookies and site data for a given container only (or for the default container without affecting any named containers).
In the end I just bought more RAM and went back to using separate profiles.
- pbronez 3y agoYeah I've had the same experience. I tried to go all-in on automated containers. I curated long regex lists to make sure things grouped the way I wanted. Ultimately it just didn't really work. The major problems I hit were: - Complex cloud services with many domains. Microsoft Office 365 uses such a bewildering collection of domains... I wound up just doing all MSFT stuff in edge. Google has similar issues. - explicit rules are too brittle. I wish it could dynamically recommend a tab family to use based on content or similar. - hard to manage. I wound up with dozens and dozens of temp container that buried my persistent, named containers. That made me rely more on the filtering rules, which required a lot of maintenance and tweaking.
- Teever 3y agoYour assessment is similar to mine. Firefox appears to have done a lot of the under the hood work necessary to bring a cool feature like this to their product, but then completely stopped working on anything beyond a rudimentary UI.
- clumsysmurf 3y agoI'm worried they will remove it, like Panorama, because I'm sure there is some code there that needs to be maintained but is low importance (otherwise they would develop it further).
- sundarurfriend 3y ago> You can't edit a container's site list, you can only add the currently loaded FQDN to it. So, you can't for example assign *.google.com to your Google container, you can only add each individual subdomain, and only after loading it. The Containerise addon lets you do both, thoug it hasn't been updated in a few years: https://addons.mozilla.org/en-US/firefox/addon/containerise/ https://addons.mozilla.org/en-US/firefox/addon/containerise/
- lost_tourist 3y agoI still find it amazing and love it. It does 90% of what I want from a silo'd experience. Sure it would be nice to have more but nothing else comes close unless you want to run multiple instances gobbling up even more ram than tabs and juggling those. I manage cookies with cookie autodelete which does much of what I want for cookie management.
- lobocinza 3y agoI prefer to use separate profiles. Containers are cool but degrade performance.
- akaij 3y agoIt seems like Sidebery is what you want. Lets you use regex matching for containers.