Chrome “clear cookies on exit” feature does not work
superuser.com
superuser.com
Fortunately in this case it looks like a good answer hasn't been deleted.
This is still NOT (fully+) fixed in current (73) Chrome/Chromium.
+) in most real usage scenarios your cookies will persist, contrary to your/users belief.
The even bigger problem, is google employees for a few years (sic!) delaying fix for this. AFAIK press article documenting it is in the works, but you can just jump into chrome bugs discussions and draw your own conclusion if this was prompt and appropriate reaction.
So the problem is:
1. it is not yet fully fixed
2. it is MULTIPLE years in this state
3. google knew about it and was interested in keeping it as it is.
https://armin.dev/blog/2019/03/firefox-extensions-browsing-d...
I discovered this recently when I logged in to website X in a Private window, then closed the window without explicitly logging out, and returned to X later that day. I had another Private window open (with a completely different site). I was still logged in to X! because that second Private window had preserved the session.
This means, of course, that sites you visit simultaneously in separate Private windows are not isolated from each other either.
I still am mostly happy with Firefox and use it daily, but this was a completely unexpected and unwelcome behavior.
The multi-account containers extension mostly solves the problem for me https://addons.mozilla.org/en-GB/firefox/addon/multi-account... though I wish it was more convenient to open a tab in a specific container, and to discard and create containers.
When adding a site to the clear-on-exist list, the box shows
[*.]example.com
[*.]reddit.com
Quite frankly we need to stop trusting apps, particularly browsers at all. ;)
Mozilla is aware - there are a few bugzilla reports open about this - but like most Firefox bugs it takes months or years to be fixed. Last year (nov/dec?) they fixed something that improved battery life, but it's still worse than Chrome for me.
I came across it when I was trying to get two totally separate Chrome installs working on one machine (using https://github.com/djbclark/chrome-schismator), in such a way that they can run in parallel, update in parallel, each totally isolated from one another. It seems as though it's not possible to have two Chrome installs update themselves separately due to the Keystone application only being able to store one reference to a Chrome install at a time, meaning that the other Chrome instance never detects that it's out of date.
# Open a new firefox instance, with a temporary profile
function firefox_temp() {
dir=$(mktemp -d)
echo "Profile directory: ${dir}"
firefox --new-instance --profile ${dir}
echo "Cleaning up .."
rm -rf ${dir}
}
But this way I'm very certain extensions, history, local-storage, etc, are absolutely not available.
(To be honest I tend to use this mostly avoid caching, and other things. Useful when you're testing redirects and new designs.)
open -Fna /Applications/Google\ Chrome.app \
--args --user-data-dir=/my_temp_profile_dir/my_tmp_profile
https://github.com/jessfraz/dockerfiles/blob/master/chrome/s...
It could be configured to run in a totally clean container to keep the browser reasonably isolated from the host system.
Of course, the truly harcore can use Qubes OS and spawn a disposable VM to browse the web from:
Personally, I'd like browsers to be much smarter about which cookies to keep and which to throw away. Keep cookies about settings, throw away everything else. And instead of not accepting cookies, leading to sites complaining about that, just accept them and throw them away at the end of the session.
Also, I'd really like the option to open some sites always in incognito mode. Many sites have no business knowing who I even am, but some really do. Same cookie policy for all sites makes no sense. Cookies need to be a lot more transparent, and instead of relying on annoying and incomprehensible GDPR popups, the browser should take care of that.
https://bugs.chromium.org/p/chromium/issues/detail?id=750452...
I don't know why anyone feel anything more than indifference about it; I find it annoying.
I used to use a tool (I think it was called RedQuits) that implemented the windows closed -> app quit behaviour.
This happens also in Chromium.
There is (proably?) a logic when cookies will be deleted, but it is under so strange conditions, that 99% of users who choose this options, DO NOT HAVE cookies deleted on chrome/quit/restart AT ALL.
:-o
I don't want the feature you describe. I prefer undo to confirmation.
[1] https://www.sciencealert.com/the-close-door-buttons-in-eleva...
Broad generalizations about nations are rarely accurate.
It has to do with the owners of the elevators choosing to override the programming.
Elevator doors are initially programmed to stay open for a period of time based on their capacity, intended use, type of building, etc...
If the owner or installer of the elevator finds this default not suitable for the environment and use, then the wait time can be changed, and/or the door close button function can be altered.
[edit] In some elevators, the reason the door close button doesn't work is because it's not meant to be used by ordinary people on an ordinary day. It's meant for when the elevator is in utility or fire mode, used by maintenance people, firefighters, moving companies, etc...
They push the door open button and the door opens, and stays open while equipment is moved in and out. The door closes when the door close button is pressed.
People assume every button is for them.
Agreed. But I was trying, by giving a counterexample, to respond to an even broader generalization: that "door buttons in elevators don't do anything". And I did say "usually".
Haven't noticed any other buttons not working though.
It might be the case that Reddit or another vendor just adds that cookie from other sites (like within a share button functionality)
I wonder if Chromium has the same problem?