> I have this option enabled and you would be surprised how many major web sites it breaks. It's caused two major outages for us. Rather insidious as well sin

> I have this option enabled and you would be surprised how many major web sites it breaks. It's caused two major outages for us. Rather insidious as well since Chrome does A/B testing and gradually was rolling this change out. > I generally address this by contacting the site admins, showing them screen dumps of their broken site and say they should demand their web devs fix this for free since their design goes against industry best practices That's just not how the world works. Sites today are a mish mash of different application engines, SAAS providers, libraries and frameworks. If the version I built on two years ago doesn't set the Same-Site property that's not my (or the vendor's) fault. They gotta pay me to upgrade to fix it. And that's hoping that everything I depend on has upgraded their stuff to fix it.