Upcoming chrome changes and breaking issues with iframes
There are some upcoming changes being rolled out to chrome in Jan 2020 involving default behavior of the samesite property in cookies, effectively making 3rd party cookies disabled by default. This can be tested now in chrome 76/77 by enabling the feature flags: go to chrome://flags search for samesite, there will be 2 flags to enable. restart browser I've tested this with the microsoft streaming content iframes and found that this does indeed break the playability of thes iframes. When i click the iframe and load the content in its own browser tab it works. Is there anyone working on a fix for this yet? For those that aren't aware of this change here is a brief summary: Google is planning to make https://www.chromestatus.com/feature/5088147346030592https://www.chromestatus.com/feature/5088147346030592to how Chrome treats cookies without the SameSite attribute. The default changes from SameSite=None to SameSite=Lax, and SameSite=None requires Secure. This is done to improve overall web security and eliminate certain classes of CSRF attacks. Details about the SameSite attribute can be found https://web.dev/samesite-cookies-explained. Changing the default means cookies without an explicit SameSite=None attribute will not be sent in a 3rd party context anymore. This affects identity scenarios in various ways and can affect other app scenarios too. Change overview: https://www.chromestatus.com/feature/5088147346030592 Intend to implement and ship discussion: https://groups.google.com/a/chromium.org/d/topic/blink-dev/6KhRNH3PrvU/discussion Google's plan updates: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromium.org%2Fupdates%2Fsame-site&data=04%7C01%7Ctarekk%40microsoft.com%7C1ced9f8c287b491e534f08d743aa717e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637052271698868346%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=2BKtr8T%2B8cg1vh7I7cpSMipiUmrXd4D%2FYYhK5ZK1Zbo%3D&reserved=0