Rowan Krishnan

@ofmarconi We're not able to reproduce this bug on Windows 10 running Chrome 103. It might be worth confirming your cookie settings in Chrome, as blocking third party cookies under...

@ofmarconi We'll be doing some more testing internally; I'll let you know whether we're able to confirm the issue.

We tested Chrome, Firefox, and Edge on an actual machine running Windows 10 (as opposed to a simulator) and are still not able to reproduce this issue. Here's the screen...

Thanks for reporting this issue @gintermaggio-am (and for putting together a Codepen). I'm able to reproduce, but because it's confined to a narrow use case, we likely won't be prioritizing...

@kasvith If possible, I would recommend following the approach that Wesley shared above for generating the embed code.

Thanks for reporting this issue, @Dima-Astreyko, and for providing clear reproduction steps. We have this bug ticketed internally for later prioritization.

We will plan to investigate this issue once it's reproducible.

Thanks for leaving this feedback @pgouldmiro. This is not a feature the SDK currently supports, but we've filed an internal ticket to explore eventually adding support.

Hi @statico - I'm not able to run Lighthouse on the page provided (it's reporting an error), and when I run it on a [raw player embed URL](https://player.vimeo.com/video/76979871), I'm not...

Interesting. I'm now seeing that result when running Lighthouse in Chrome's developer tools: But I'm seeing different results when running Lighthouse via Chrome extension (top) and PageSpeed Insights (bottom): Not...