Some cookies misusing the recommended "SameSite" attribute

[2bndy5]

In Firefox v113.0.1 (when browsing the social plugin's docs), I noticed a few warnings in the dev console:

Some cookies are misusing the recommended “SameSite“ attribute 4
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:27:576
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:27:576
Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:27:576
Cookie “_gat” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:27:576

I'm not sure if this was intentional or simply unaddressed.

It is also worth noting that my LAN uses a DNS sinkhole in which traffic to/from the google-analytics domain is blocked. So, I also see these warnings/errors in the Firefox dev console:

Cookie “_ga” has been rejected for invalid domain. analytics.js:27:576
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://www.google-analytics.com/j/collect?v=1&_v=j100&aip=1&a=806423225&t=pageview&_s=1&dl=https%3A%2F%2Fsquidfunk.github.io%2Fmkdocs-material%2Fsetup%2Fsetting-up-social-cards%2F&ul=en-us&de=UTF-8&dt=Setting%20up%20social%20cards%20-%20Material%20for%20MkDocs&sd=24-bit&sr=1920x1080&vp=1173x893&je=0&_u=QACAAEABAAAAACAAI~&jid=1393347329&gjid=2133052323&cid=667973455.1683411965&tid=UA-73586301-1&_gid=1642272398.1683933218&_r=1&_slc=1&z=600682413. (Reason: CORS request did not succeed). Status code: (null).

[squidfunk]

Well, those are all cookies from Google Analytics, so maybe report to Google? Material for MkDocs doesn't set any cookies.

[2bndy5]

Thanks, I wasn't sure what to make of those warnings or where the cookies were coming from.

Unfortunately, my DNS sinkhole makes reporting this a hassle for me, more than it is probably worth. TBH, I can keep ignoring them, hoping they're aware of it or will be.

[squidfunk]

Universal Analytics is being sunset by the end of June anyway, we still need to make the switch. I think you won't see them on Google Analytics 4, which is the new version.