You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've used aurora.js for years on my site and it has worked well. I now get the following notice from the console when using Chrome:
'A cookie associated with a cross-site resource at http://74.192.166.68/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.'
I don't use cookies on my site, other than those in aurora.js .
One Mac user has already encountered a problem. I'd rather ask the aurora authors to comply with the new browser rule than try to fix it myself. Chrome claims other browsers will soon adopt this restriction.
Any guidance is appreciated. [email protected]
The text was updated successfully, but these errors were encountered:
I've used aurora.js for years on my site and it has worked well. I now get the following notice from the console when using Chrome:
'A cookie associated with a cross-site resource at http://74.192.166.68/ was set without the
SameSite
attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set withSameSite=None
andSecure
. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.'I don't use cookies on my site, other than those in aurora.js .
One Mac user has already encountered a problem. I'd rather ask the aurora authors to comply with the new browser rule than try to fix it myself. Chrome claims other browsers will soon adopt this restriction.
Any guidance is appreciated.
[email protected]
The text was updated successfully, but these errors were encountered: