I am using fathom on another (sub) domain than my primary domain. I believe most of the other users would be doing the same. Browsers are planning to phase out third party cookies and the solution proposed includes using SameSite=None and secure attributes in cookie.
As Fathom tarcking script creates the script (with the domain registered as site) with JavaScript, in my case considered as a third party cookie but without the samesite and secure attributes.
Firefox gives this warning,
Cookie “_fathom” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
I am using fathom on another (sub) domain than my primary domain. I believe most of the other users would be doing the same. Browsers are planning to phase out third party cookies and the solution proposed includes using
SameSite=None
andsecure
attributes in cookie. As Fathom tarcking script creates the script (with the domain registered as site) with JavaScript, in my case considered as a third party cookie but without the samesite and secure attributes.Firefox gives this warning,
Cookie “_fathom” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite