There are some quite big changes in Chrome 80, and later on in Firefox/Edge(With Chromium), that affects cookies.
Some good litterature here:
https://devblogs.microsoft.com/aspnet/upcoming-samesite-cookie-changes-in-asp-net-and-asp-net-core/
https://www.chromium.org/updates/same-site
https://auth0.com/blog/browser-behavior-changes-what-developers-need-to-know/
This will break quite a few flows that might not be Episerver specific, but a few things Episerver uses are also affected. For example Episerver Commerce relies on anonymous identification and the anonymous identication module does not seem to be updated to set the SameSite cookie attribute, so will potentially break in some browsers affecting carts and so on. Also it seems using the content delivery api could also be affected depending on how you use it.
I tried both the Chromium beta channel and also enabled the SameSite feature flags in current Chrome browser and there is quite a few warnings in the developer console about cookies being blocked which will affect various features in Episerver and its addons is my guess.
So my question to Episerver and the community is: what have people done to mitigate this? Have you experienced any breaking stuff in your current solutions when using the beta versions of Chrome?