Feature request: Ability to clean cache and other stuff per container

[rahmanshaber]

If there is ability to clean the cache and other stuff by per container will be great help.

I use goggle search in a container and if there is a way to clear the cache just only within that container will be very helpful as i don't wanna do clean up the whole browser as if i do it i need the re-login.
just want clean the cookies, cache and other on the container i use goggle search.

[ameaninglessname]

Try this add-on : Cookie AutoDelete
GitHub repo

[jay0x]

@ameaninglessname It will not work in all cases. For example, some sites make 3rd party cookies or super cookies. There are no way to find out that to delete without a research. It would be great to have a feature to purge a container from time to time.

[rahmanshaber]

Yes, i keep those google search in a container and ability to clean that container will be great from the same add-on.

[GemKosan]

I found an extension that might be a good workaround:
https://addons.mozilla.org/en-US/firefox/addon/clear-private-data-now/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search

[josegfv]

This is definitely a needed feature to add, it will be great to select the container and do a clear cache only for the cookies and data related to the specific container.

[winks]

+1, but for a specific reason, and that's why I think the proposed addons don't work, at least in my case. (cookie autodelete would make me not stay logged in, and for "clear private data now" I suppose the website would have to load first, but read on...)

I've now had it repeatedly (3 times for Slack, but at least once for another website) where something went completely haywire and I couldn't access the page anymore, but all other pages (except the one I was confining to the container, ironically) still worked. I think it has something to do with ssl certs, or maybe cookies or webworkers the cache (NS_ERROR_DOM_ABORT_ERR), but if it happens I have to nuke the container right now (because there's nothing wrong with my connection, it works in another container, or the raw profile or another browser). Not the end of the world and certainly not as bad as having to nuke the profile (if cleaning wouldn't help), but a little annoying.

Edit: 3 days later, it happened again, on another machine, and this seems to be the culprit: https://support.mozilla.org/en-US/kb/how-fix-error-when-trying-open-telegram-or-slack - so maybe ignore what I wrote, but nuking cookies and the cache has also helped in the past, and my problem was indeed mostly related to Slack and I've never had it outside of a container, but then again it's been a while since I logged into Slack without a container iirc...

[FOSS-Love]

#303 duplicate

[dannycolin]

Closing as duplicate of #303. For the "other stuff", there's already a couple of other reports filed for history, cookies, etc. It's better to keep one feature request per report.