Forum Discussion
Dev channel update to 88.0.685.3 is live
josh_bodner You note that Edge would sometimes clear cookies on the do not clear on exit list. I have seen this but infrequently. The problem with the current dev and canary builds, and one which has repeatedly appeared in earlier builds, is that cookies are not cleared on exit at all. I have a list of five exceptions but find that on start after all windows closed that I could have dozens of domains with cookies and local storage.
I also have an issue with stable that a domain that sets local storage only but no persistent cookies and is in the exception list will have the local storage cleared on exit. This site does set session cookies.
And while on the subject, why does the exception list on edge://settings/clearBrowsingDataOnClose not sync across installations while the lists on edge://settings/content/cookies do roam?
Rich
josh_bodner I looked at this more closely. It appears that the hosts on edge://settings/siteData which are inappropriately present on start up after closing all Windows, that each has local storage but zero cookies. This may be file storage or database storage or combinations of storage not cookies. Here is one example.
rshupak I've already got a thread with the engineers about various "clear browsing data when closing the browser" bugs, so I'll ask them about this!
To be clear, I have two opposite issues in different channels.
In Edge stable, Version 86.0.622.61 (Official build) (64-bit), sites in the do not clear list have their storage cleared on exit when it shouldn't be. This may be related to the fact that the site in question has cookies but all are session only not persistent.
In Edge canary, Version 88.0.689.0 (Official build) canary (64-bit), sites not in the do not clear list retain their storage across exits. Their persistent cookies are cleared. It looks to be as if the storage only, albeit multiple types of storage, are retained when it should be cleared. Sites in the do not clear list do have their cookies preserved.
rshupak Let's focus on the Canary issue for now since we've made quite a few fixes that might not be in Stable yet around the first issue. If you haven't yet, can you file feedback for it so we can get a bug in our database?
As for your other post, I'll make sure the team knows about them as well, but I'm curious why you expect only cookies with the secure attribute to be preserved.
