New Feature in Edge: Provide option to keep specific cookies when closing Edge browser
This feedback item is now available in Microsoft Edge Version 83.0.470.0 (Official build) canary (64-bit) Status Feedback On this list for Planned for March Provide option to keep specific cookies when choosing to clear browsing data on close 19 weeks edge://settings/clearBrowsingDataOnClose You've allowed the following sites to save and read cookies on your device. Cookies for these sites won't be cleared when you exit the browser.[Resolved] Adding cookies to the Allow list makes them bypass the 3rd party cookie blocking !?
When I turn on 3rd party cookie blocking, and add [*.]youtube.com [*.]google.com to the allow list of cookies this causes Google and YouTube cookies to be read and accessed in Reddit and other sites, Even though 3rd party Cookie blocking is enabled. Edge (or Chromium in general, since it happens on Chrome 88 stable too) is confused. that Allow list is for allowing certain cookies to enter or stay in the browser, the Allow list is Not a 3rd party cookie bypass list. my actual setup and configuration was more complex but I had to do lots of testing to find out why Reddit still detects and asks me to sign into my Google account when 3rd party cookie blocking is enabled!
Cookieless browsing broken after update KB4580979
Upon running Windows Update KB4580979, .Net 4.7.2 projects that have the SessionStateSection.Cookiless Property set to AutoDetect no longer functions as expected. Previously, a browser that blocked cookies would be redirected to the same page with the querystring /default.aspx?AspxAutoDetectCookieSupport=1 and upon the system detecting that cookies were not supported it would redirect again to a cookiless session URL e.g. /(X(1)S(adl04pietheradyfawfaqlym))/default.aspx?AspxAutoDetectCookieSupport=1 Since the update, a browser would continously be redirected to /default.aspx?AspxAutoDetectCookieSupport=1 until the redirects exceeded the maximum redirects. Relevant Web.config section: <configuration> <system.web> <sessionState cookieless="AutoDetect" /> </system.web> </configuration> Windows Server 2019 DataCenter Version 1809 OS Build 17763.1369Add the ability to import cookies and browser sessions between different channels of Edge browser
This would be a quite useful feature since people don't have to reauthenticate in every website once they change browser or decide to use the insider channels instead of stable. it'd be even better if you let Edge import cookies and browser sessions from different browsers.Add Cookies import option when importing data from other browsers
It'd really help me to resume my work quickly in Edge if I could import cookies from other browsers to Edge, so I wouldn't need to login to all of the websites again and deal with their 2step verifications etc. I've used Yandex browser and it supports this feature, very helpful and convenient. so please Add it to Edge[Suggestion] Tab Groups act like Containers
Love tab groups for staying organised when I use Edge, but I feel they would be more useful if they acted like containers in Firefox. Let them have their own cookies and add a context option to open link in a tab group or set a domain to always open in a tab group. Of course, this would require the browser to remember tab groups when closed. See; https://addons.mozilla.org/en-US/firefox/addon/containerise/ (addon which allows you to set domain patterns to always open in specific containers) https://addons.mozilla.org/en-US/firefox/addon/temporary-containers/ (addon which creates a temporary container that deletes when the last tab with that container is closed - it will delete history and cookies)Some parts of the Privacy Sandbox land on Edge Canary
This flag edge://flags/#use-first-party-set which was added today to Edge Version 89.0.749.0 (Official build) canary (64-bit) it's one of many privacy-related features for Privacy Sandbox, the goal of which is to ultimately get rid of 3rd party cookies. Use First-Party Sets First-Party Sets are sets of registrable domains (or origins). The browser uses these sets to allow websites that have multiple domains to treat their related domains as if they were first-party domains. This enables less restricted cross-domain communication across all the domains in a First-Party Set. – Mac, Windows, Linux Enable domains to belong to the same first party Goal: Enable entities to declare that related domain names are owned by the same first party. Many organizations own sites across multiple domains. This can become a problem if restrictions are imposed on tracking user identity across sites that are seen as 'third-party' but actually belong to the same organization. First Party Sets aims to make the web's concept of first and third parties more closely aligned with the real world's by enabling multiple domains to declare themselves as belonging to the same first party. more info: Digging into the Privacy Sandbox (web.dev) privacycg/first-party-sets (github.com)Cookieless browsing broken after update KB4580979
Upon running Windows Update KB4580979, .Net 4.7.2 projects that have the SessionStateSection.Cookiless Property set to AutoDetect no longer functions as expected. Previously, a browser that blocked cookies would be redirected to the same page with the querystring /default.aspx?AspxAutoDetectCookieSupport=1 and upon the system detecting that cookies were not supported it would redirect again to a cookiless session URL e.g. /(X(1)S(adl04pietheradyfawfaqlym))/default.aspx?AspxAutoDetectCookieSupport=1 Since the update, a browser would continously be redirected to /default.aspx?AspxAutoDetectCookieSupport=1 until the redirects exceeded the maximum redirects. Relevant Web.config section: <configuration> <system.web> <sessionState cookieless="AutoDetect" /> </system.web> </configuration> Windows Server 2019 DataCenter Version 1809 OS Build 17763.1369
