Notices in console about cookies

[cibulka]

Expected Behavior

Working player without notices in console. Also, could you explain in docs how the player uses cookies and what it actually tracks?

Actual Behavior

This notice in Chrome's console:

56:1 A cookie associated with a cross-site resource at http://vimeo.com/ 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.

This notice appears also with setting dnt: true on init.

Steps to Reproduce

https://nest-forgottenwar.cibulka.now.sh/cs/story/nuda-selfie-zelezo/120

Thanks!

[alexluong]

I have the same question too. Would love to be part of the discussion. Thank you!

[thewiremonkey]

Same question.

Seeing the same issue here

[mikkopori]

Same problem here. A solution would be good.

Perhaps adding a header like recommended here could be the solution?

https://stackoverflow.com/a/58320564/7225808

[teds31]

Is anyone working on this?

[luwes]

sorry for the late reply, we're aware of this warning in the console and are actively looking how this can be resolved. note that the warning is just informative, we have not experienced any issues with the player due to this new feature in Chrome.

[hhimanshu]

We are getting this warning too

[luwes]

@cibulka we made some changes that should resolve it, at least on the player.vimeo.com domain.
how is it looking on your end? thanks

https://player.vimeo.com/video/76979871

[joshmckibbin]

The issue still remains on player.vimeo.com domain

[luwes]

@joshmckibbin have you tried clearing browser cache?
also try changing the volume of the player, this will reset the player cookie.

as a last resort clear all cookies under the .vimeo.com domain. load the player again and check.

[joshmckibbin]

@luwes actually it seems to be fixed now. Thanks!