I just recently noticed the error referenced in the subject line popping up in my console window. The error I’m getting looks like this:
Cookie “CF_CLIENT_COM_SELECT184” 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/Cookies debtor
Cookie “CF_CLIENT_COM_SELECT184_LV” 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/Cookies debtor
Cookie “CF_CLIENT_COM_SELECT184_TC” 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/Cookies debtor
Cookie “CF_CLIENT_COM_SELECT184_HC” 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/Cookies debtor
Cookie “CF_CLIENT_COM_SELECT184_LV” 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/Cookies util.cfc
Cookie “CF_CLIENT_COM_SELECT184_TC” 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/Cookies util.cfc
Cookie “CF_CLIENT_COM_SELECT184_HC” 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/Cookies
I checked in multiple browsers to see if the same error was being generated and it’s identical across them all.
It hasn’t broken any of the features of my app, at least not yet. I’m not sure where I’d go to even correct such an error.