Hi @jankoulaga, I think there are two distinct points:
- Is upgrading to 0.16.0 going to cause degradation in the data?
- Is there a better way to set the
I’ll address them in turn.
Is upgrading to 0.16.0 going to cause degradation in the data?
You are correct that setting
SameSite=None might lead to loss of third-party cookies on iOS devices before iOS13. As the bug report you linked to suggests, the attribute might be treated as
However, let’s look at the alternative. If you do not upgrade, and stay on 0.15.0, you will have no control over the
SameSite attribute. On Chrome 80 and later, a missing
SameSite attribute will be interpreted as
SameSite=Lax by default, which again will result in the loss of third-party cookies.
So either way, because of the current state of the browser world, there’s this tradeoff, which is independent from whether users upgrade to 0.16.0 or not. They’ll have to decide which is likely to impact them more: no third-party cookies in iOS <13 or no third-party cookies on Chrome 80+.
Is there a better way to set the
We always welcome PRs from the community! But the approach with user agent sniffing is likely to be very hard. Almost all browsers engage in some sort of user agent obfuscation, so that is a very unreliable way of detecting the browser. And even if we can come up with something that works in the current moment, there are no guarantees that browsers won’t make arbitrary breaking changes.
Does that make sense?