8 ms·
Chrome “clear cookies on exit” feature does not work
- paulpauper 8y agoStill waiting for Google to add a feature to display a warning alert box when you try to close all tabs by accident, but a decade later no such feature exists even though everyone wants it, and Firefox has it, and it seems trivial to implement.
- intellix 8y agoIf you CMD Q on osx you get a warning
- mrweasel 8y agoWhich is annoying. I though that would be a good idea, because I occasionally closed a browser by accident. In reality I more often than not actually want to close Chrome, and the "press and hold cmd+q" is pretty annoying.
- stordoff 8y agoOn the flip side, I often hit it accidentally when hitting cmd-w, and I don't think I ever intentionally hit it. Choosing good defaults is hard.
- sowbug 8y agoControl-shift-T when you start Chrome back up again. I don't want the feature you describe. I prefer undo to confirmation.
- wurst_case 8y agoReminds me of door control buttons in an elevator that you use everyday only to find the button resting on the floor one day, revealing that it was adhered to the control panel with a hot glue gun the whole time.
- deleted 8y ago[deleted]
- wastholm 8y agoI keep hearing that, and apparently that's the case in the US [1]. In Japan, the buttons are usually very much operational and they have devised a whole system of etiquette around them. [2] [1] https://www.sciencealert.com/the-close-door-buttons-in-elevators-don-t-actually-do-anything https://www.sciencealert.com/the-close-door-buttons-in-eleva... [2] https://boingboing.net/2017/10/12/button-mashing.html https://boingboing.net/2017/10/12/button-mashing.html
- RandomGuyDTB 8y agoThe US buttons don't work because there are mandatory waiting times for the doors closing due to the ADA ((your article mentions that)) - they're still normally plugged in.
- ams6110 8y agoI've been in elevators where they definitely did work, with immediate effect. But also some where they don't seem to do anything.
- reaperducer 8y agothat's the case in the US [1]. In Japan 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.
- rdslw 8y agoThis happens for a few years (much older than URL in question). 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
- RandomGuyDTB 8y agoDo you have any citations as to how old the issue is?
- celsoazevedo 8y agoI've been using an extension called "Auto History Wipe" for almost two years because of this bug, so it's at least ~2 years old.
- r3bl 8y agoAt least since July 2017, when this bug was opened: https://bugs.chromium.org/p/chromium/issues/detail?id=750452 https://bugs.chromium.org/p/chromium/issues/detail?id=750452
- omosubi 8y agoHopefully this spurs more than a few people to move to Firefox. Im not looking forward to an all chrome/chromium future
- dessant 8y agoI agree that more of us should use Firefox, though if you're switching because of this bug, you may be in for some disappointment. https://armin.dev/blog/2019/03/firefox-extensions-browsing-data-security/ https://armin.dev/blog/2019/03/firefox-extensions-browsing-d...
- est31 8y agoThose bugs are all extension bugs. The built-in option to "clear data on exit" that Firefox has in about:preferences seems not affected by them. Although of course they should be fixed.
- deleted 8y ago[deleted]
- KKKKkkkk1 8y agoBut it is affected. It's very easy to confirm that even with "Clear data on exit" activated, websites recognize you across sessions.
- OnlyRepliesToBS 8y ago
- sasasassy 8y agoThis is most likely a website keeping the same data in HTML5 web storage, flash cookies or other, and when noticing one of them has been removed, repopulating them. These are also sometimes called super, zombie or persistent cookies.
- icebraining 8y agoIt seems it was kept in IndexedDB, but Chrome was only cleaning it up when you closed it and not when you closed all its windows (I didn't even know there was a difference). https://bugs.chromium.org/p/chromium/issues/detail?id=750452#c22 https://bugs.chromium.org/p/chromium/issues/detail?id=750452...
- OJFord 8y agoThere is on macOS, (for all 'apps', not just Chrome) but not, I think, on any other platform. 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.
- cm2187 8y agoHold on. The setting is called “keep local data only until you quit your browser”. Not “local cookies”. And that’s always how I expected it to work. If it preserves data from web storage or others than this is either a massive fuck up or a disingenuous placebo setting.
- toyg 8y agoI believe handling of Flash cookies is completely outside the browser.
- votepaunchy 8y agoFlash is bundled with and sandboxed by Chrome.
- fouc 8y agoPerhaps we need a way to delete chrome, re-install it, and then re-populate w/ the exact cookies we want persisted. Nothing else. No chance for web storage or other hidden/zombie cookies. This could be done every time the app is closed. Quite frankly we need to stop trusting apps, particularly browsers at all. ;)
- tqkxzugoaupvwqr 8y agoThere is a flaw in your proposal: Deinstalling doesn’t necessarily ensure all program data is removed (at least on desktop OSes). When you reinstall the program, your previous program data can still exist and be used as is. So the persistent cookies can actually be super persistent in that they survive the program removal.
- GrayShade 8y agoPerhaps you should use Firefox.
- tssva 8y agoPerhaps Firefox should finally get around to not being a destroyer of performance, stability and battery life on a large subset of MacBooks, so people such as myself can use it.
- jhasse 8y agoNah, they rather implement a file sharing website.
- mrweasel 8y agoI honestly never had that problem, sure performance wasn't great 5 or 6 years ago. I've used Firefox as my primary browser for at least five years, switching from Chrome when performance started to improve for Firefox.
- OJFord 8y agoI have Firefox (with accidentally permanently 50+ tabs open) on a touch bar MBP and it's fine.
- JdeBP 8y agoDeleted by SuperUser diamond moderators are two answers dated 2019-02-10 that point to the exact bug report in the Chromium bug reporting system for this. The Chromium bug report that the deleted answers point to is listed as fixed as of 2019-02-18.
- viraptor 8y agoCould you post those links?
- tacomonstrous 8y agoA search on the Chromium issues page shows this: crbug.com/750452
- musicale 8y agoI've also noticed a persistent problem with stackexchange sites where useful information is deleted, appropriate questions are unnecessarily closed, locked, etc. by moderators. Fortunately in this case it looks like a good answer hasn't been deleted.
- anoncake 8y agoSounds like these replies didnt answer the question and should have been comments.
- rdslw 8y agoUnfortunately, this is not true. 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.
- jbverschoor 8y agoWhy are cookies even persisted on disk in the first place when such an option is enabled?
- colejohnson66 8y agoI’m guessing here, but maybe it’s in case of a crash, it can reload them back when you reopen the browser?
- adem 8y agoI can imagine that multiple tabs/windows don't share the same address space, so in case of opening the same website on another browser instance, saving to disk would make sure that the cookie is exposed to other running processes as well.
- GordonS 8y agoSaving to disk is probably one of the simplest ways of sharing data between processes, but it's far from the only one (e.g. named pipes)
- RandomGuyDTB 8y agoIf the cookie is stored in-file somewhere you could probably make a batch file to delete it and then start chrome and put the shortcut on your desktop and in your start menu.
- r4u 8y agoIt has never worked - and it probably will newer work. Google wants your data.
- deleted 8y ago[deleted]
- electrichead 8y agoSerious question, is this a bug in Chrome that affects all cookies or is it something specific to that reddit.com cookie? It might be the case that Reddit or another vendor just adds that cookie from other sites (like within a share button functionality)
- TingPing 8y agoAs another comment pointed out there is no bug. reddit.com and www.reddit.com are different origins.
- gcb0 8y agogood time to remember that Google employees silently rolled back, over years, every single attempt by chromium contributors to block or add privacy features (e.g. restrict to same domain) for the referrer http header (which is the basis of Google ad business)
- wdr1 8y agocrbug.com/750452
- d2p 8y agoI posted an answer on SO but may be worth repeating here. The screenshots show "reddit.com" as clear-on-exit and "www.reddit.com" as the owner of the cookie. When adding a site to the clear-on-exist list, the box shows [*.]example.com I think you need to use [*.]reddit.com if you want to include sub-domains too.
- musicale 8y agoDisadvantage for web users who care about privacy; advantage for advertisers and adtech companies that want to track you. I wonder if Chromium has the same problem?