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.

[ghost]

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!

[darylknight]

This still happens if you're embedding a background video from Vimeo Pro using the external download link. Header video on https://qeprize.org is causing it.

[ConversionWars]

Confirmed still happening for me with a vimeo video BG

[spidercreations]

Same issue when embedding Vimeo Pro videos into a background slide within Slider Revolution. https://brownstonepark.com and https://powderridgepark.com

[ryearsley]

Same issue. Using API to pull in videos and embed. https://www.breathehotyoga.com This will become a serious issue for our business especially since we're now depending more on video due to the Covid-19 measures in place. We are located in Seattle and all of our studios are shut down.

[martinweck]

+1 for me. Thanks for looking into it!

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.

[Hanley1]

Starting to get more messages from visitors who can't load some of our videos. One of the visitors reported the same thing happening with Vimeo players on other sites as well. I think it's safe to say this has gone beyond just being a warning, and the reports will only increase over time as Chrome rolls out this update to more people.

[truskowc]

+1

“vuid” is the cookie, fyi

[danielucas]

+1 still no movement on this?

Getting messages from users on our site as well that videos (using HTML5 player, not iframe embed) aren't playing.

[hemilsheth]

Any updates for Vimeo samesite cookie issue, I dont seem to find the solution, we have to urgently fix this as Google is going to roll out changes on July 14, 2020.

[luwes]

thanks for all the feedback, we are in process of resolving this issue. by the end of the day the vuid cookie will be updated to have the proper SameSite attribute.

however there are still several 3rd party cookies (Google Analytics) loaded when you have visited the main website vimeo.com, these are created under the cookie domain .vimeo.com. subsequently whenever a Vimeo player embed (player.vimeo.com) is loaded via the iframe those cookies are also loaded and Chrome will show the warning because they don't have the SameSite attribute yet. these 3rd party scripts will be updated by the vendors soon but it's worth to point out that these cookies are not used in the player and will not cause any issues.

please let me know if you have any questions.

[wesort]

Thanks. I know this has been a long time coming (long been seeing that console warning) so it's good to see this getting resolved. .ben.

…

On Tue, 30 Jun 2020 at 20:18, wesley luyten ***@***.***> wrote: thanks for all the feedback, we are in process of resolving this issue. by the end of the day the vuid cookie will be updated to have the proper SameSite attribute. however there are still several 3rd party cookies (Google Analytics) loaded when you have visited the main website vimeo.com, these are created under the cookie domain .vimeo.com. subsequently whenever a Vimeo player embed (player.vimeo.com) is loaded via the iframe those cookies are also loaded and Chrome will show the warning because they don't have the SameSite attribute yet. these 3rd party scripts will be updated by the vendors soon but it's worth to point out that these cookies are not used in the player and will not cause any issues. please let me know if you have any questions. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#482 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA55B7RQSSN4TRRUUYHAOFTRZI26ZANCNFSM4JAHD34Q> .

[proton1k]

Just for your information, might be useful to someone coming now. We used 3-rd party service fo parsing and accepting cookies and it managed to parse Vimeo cookies into Marketing group. If a user rejected Marketing type cookies, the video was not loaded. Thus we fixed the issue by setting up the correct cookie type as Necessary so that unavoidably the video was never blocked.

[repher]

Hello! Is this resolved? A client just called and after a review, the problem still exists ...?
Thanks!

[RaulRueda]

Over a year without a solution or response 🙄

[rkrishnan8594]

Hey all - apologies for the lack of activity on this issue. As @luwes mentioned in his last comment, these warnings are being caused by third party cookies set on vimeo.com, not cookies that are being set by the player, so this would not have an impact on playback. Regardless, the team has a ticket prioritized to look into adding the SameSite attribute to those cookies, which would resolve this warning.

[brown2020]

Has there been any progress on this? It has been 6 months.

[duncandejong]

Any updates?

[KjellMorgenstern]

I cleared all Vimeo cookies, obviously then player.js will not trigger the error.
I then went to vimeo.com, logged in and navigated along several vimeo.com/* pages.
Still no no cookie cross-site request / errors anymore on the site with embedded player.js.
This looks like the cookies on vimeo.com now have proper SameSite attributes that don't cause issues with player.js.

[sansari]

This is still happening. Still no solution?