Looking for other third-party SPs that fail with stricter SameSite settings

[Cantor, Scott]

> So not sure what to make of that.  Seems like Chrome and FF's behavior have
> diverged.  And so not entirely clear to me whether Chrome is really truly
> working here - and will continue to work when Chrome is settled into its final
> default state - vs is there some issue with the testing methodology that is off
> (e.g. SameSiteDefaultChecksMethodRigorously isn't doing what it claims).

Yes, that's certainly odd. Any evidence they're only setting SameSite for Chrome? I didn't trace it to check.

-- Scott