It would be nice if we could configure a container to auto-clear cookies/localStorage at the end of session. This is especially useful for the Shopping container, where travel booking websites track to give you a different price for the same trip everytime you search (national express is a good example).
A more useful feature for the specific use-case I've mentioned would be clearing cookies/localStorage periodically.
I would very much like to see the entire "Privacy & Security" setting be container-relative. In other words, the top-most option on that page should be the container name where the below settings are applied. That would simplify the UI and make it very clear how settings are configured per container. It really should be the parent option to all these settings. This would provide immense control and granularity, which is the goal of the container experiment.
This is a feature I looked for immediately after I started using containers. A long time ago I have learned to instinctively launch private mode whenever I do research online (I don't want a million tracking cookies associated with my browser instance from random websites opened for a few seconds while searching). This however presents various usability problems. Containers are an excellent solution - I assign ddg/google to a dedicated container, and whenever I navigate to a website I consider secure, the site switches to the personal container. However, cookies and browsing history still get permanently associated with the "throwaway search" container, and an option to have them automatically purge (preferably, with an ability to whitelist domains) would make this perfect for my use case.
This would be a great feature, especially for the default container.
It's been almost 4 years. The most important container feature is still not here :(
For this very reason I have given up on containers and am now using different profiles, clearing cookies when closing the last window/tab of a given profile.
Most helpful comment
I would very much like to see the entire "Privacy & Security" setting be container-relative. In other words, the top-most option on that page should be the container name where the below settings are applied. That would simplify the UI and make it very clear how settings are configured per container. It really should be the parent option to all these settings. This would provide immense control and granularity, which is the goal of the container experiment.