
"Permanent" Container behavior
I would be grateful for some information on container behavior, i.e. I created "permanent" (as opposed to temporary) containers for sites where I want that site's cookies & site data preserved in a container, so I can click "Clear Cookies/History" (or "Clear... when Firefox closes) and the items stored in PERMANENT containers are left alone, while all else is deleted. "Clear ...." doesn't appear to be respecting the permanent containers I have set up precisely to preserve these sites' cookies & data.
I'm not sure what the point of Permanent Containers is, if not to preserve those sites' data, for the sites' later use when you set Firefox to Clear Cookies and Site Data whenever Firefox Closes (or Clear Cookies & Site Data with one click). I expected it to respect data in Permanent containers, as exceptions. Else why not just use separate Temporary Containers for everything? Why bother with Permanent Containers if everything is going to be deleted when Firefox closes, whether it's marked "Permanent" or not? Is there a solution for this? Thanks, -AnneF
All Replies (3)
Hello.
Could you please clarify, what "permanent containers" are you talking about? If you refer Firefox Multi-Account Containers extension, there is no such feature.
Thanks so much for your reply, Denys. Perhaps I should have titled my question as Firefox's behavior toward permanent containers, when clearing site data.
I AM talking about Firefox Multi-Container Extension, but I'm not speaking of a feature of Multi-Account containers; I was asking about a feature of Firefox, itself (Clear ...data... When Firefox Closes). "Permanent" is a word Firefox used to describe these assigned and named containers that do not disappear, like temporary containers do.
My understanding is that these containers are permanent (as opposed to temporary) isolation buckets, or containers, where I can keep data, such as cookies, from websites that are assigned to a particular permanent container, so that no other website, except a site assigned to that container can access anything in there.
What the sites assigned to that container would keep there, presumably, is data related to my interaction with that website, such as cookies for my site preferences, shopping cart, wish lists, my computer ID for when I login, etc. If I didn't want the container to remember and KEEP these things, I could just have used a Temporary Container on the fly to isolate the data temporarily, while I was using it.
I would like to set up Frefox to automatically clear cookies and site data. etc. when Firefox closes (or when I ask Firefox to clear that data). However, of course I do NOT want Firefox to delete site data that I want to be available for the next time I re-visit a site to which have assigned a permanent container. Firefox should know to treat permanently assigned containers as Exceptions and not delete the data saved there for my next visit to that website. However, it doesn't appear that Firefox thought of this. Firefox just wipes it all away, so I lose my banks' recognition of my computer, adding steps to my login; I lose my wish lists, my preferences, my shopping carts, etc.
Is there no way to tell Firefox to NOT delete data that I have assigned to a permanent container - that is, a container to which I have assigned a permanent name, so it's contents will be preserved, unlike a temporary container?
Maybe I have misunderstood what named containers are for - what exactly they do that Temporary Containers can not do?
Thanks, AnneF
Modified
Ok, now I understand you.
The thing is, the Containers' idea is different. Basically, all Containers are the same: each of them has a separate storage for site data. That means, cookies downloaded by one Container are not available to other Containers.
Additionally, you can assign sites to Containers, setting Firefox to always open certain links in certain containers. And, in case of limiting a Container to designated sites, set Firefox to always open any non-whitelisted links outside the container (when trying to open such links inside).
This has nothing to do with history/cookies/data clearing. Multi-Account Containers were not designed with that in mind.
Modified