Forum Discussion
MicrosoftDev channel update to 88.0.685.3 is live
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.
Microsoftrshupak 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.
- josh_bodner
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.josh_bodner I've probably reported this over a dozen times. It better be in the database.
One more bug. For all but one of the exceptions in my do not clear list, I have them configured as https://example.com because the only cookies I want retained are associated with the root of the domain not hosts within them which I want cleared. I have one example where the important data, which is storage not cookies, is included as https://www.example.com. After exiting and restarting canary, I see the storage for https://www.example.com is preserved, the functionality broken in stable. What is also preserved and should not be are cookies associated with https://example.com. I purposely did not add https://[*.]example.com to the do not clear list as I want the specific host and only this host retain persistence.
There is another bug which I haven't mentioned or reported before. This is a different domain in my do not clear list also expressed as https://example.com. The bug is that cookies without the secure attribute are preserved. They should not be.
