4 ms·

I have this option enabled and you would be surprised how many major web sites it breaks. We can blame chrome and safari all we like, but the real blame is on

I have this option enabled and you would be surprised how many major web sites it breaks. We can blame chrome and safari all we like, but the real blame is on web devs who had 1-2 years to fix this and just can't bother (until forced by Google or Apple). Edit: 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 (I often include link to Mozilla article on this). If that doesn't help, I try again with the higher ups, telling them their store have silently been rejecting paying customers and their IT people have refused to fix it. This usually fixes the issue quickly, only to come back after the next major site update.

zelphirkalt 6y ago
While I agree that much is on the web developers, there is also management to blame for not allowing time for fixes, until stuff is truly broken and lies in pieces.
hombre_fatal 6y ago
Requiring the whole world to change instead of just changing a choke point like three major browsers is an unreasonable ask and only postpones actual progress. Nothing is tangible to anyone until something is broken.
treis 6y ago
> 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.

zelphirkalt 6y ago

While I agree that much is on the web developers, there is also management to blame for not allowing time for fixes, until stuff is truly broken and lies in pieces.

hombre_fatal 6y ago

Requiring the whole world to change instead of just changing a choke point like three major browsers is an unreasonable ask and only postpones actual progress. Nothing is tangible to anyone until something is broken.

treis 6y ago

> 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.