4 ms·

Can you give some examples with specifics on how their changes are causing problems? I only recently became aware of the SameSite setting and was considering us

• hirsin 7y ago
  If you have cookies that need to be read in a 3p context (federated auth for instance), you must UA sniff in order to figure out if setting samesite=none is going to break your cookies, do nothing, or be required for your cookies - just across three versions of Chrome. Then there are the apps that forked Chromium 66 and then renamed it, so you can't tell what version it is. We're planning to just break them, since it's impossible to tell what to do there.
• will4274 7y ago
  If you return SameSite=None to Chrome 66, it ignores the cookie entirely. If you return SameSite=None to iOS 12, it treats it as SameSite=Strict. At the time each software was written, the behavior was blessed by the spec ("None" wasn't yet a valid value).
  • cpeterso 7y ago
    Here is Google's current list of incompatible clients. Someone should write an npm or Python module that encapsulates all these exceptions so sites can decorate their cookies correctly without worrying about these details. https://www.chromium.org/updates/same-site/incompatible-clients https://www.chromium.org/updates/same-site/incompatible-clie...