Brad Dougherty
Brad Dougherty
Hmm, nothing immediately jumps out to me, other than you don't need to call `player.ready()`, but that shouldn't make a difference here. Are you able to reproduce the issue when...
@dlueth can you file a separate issue for that with reproduction steps and example? Thanks.
I think the issue here is this code sending a message to the player on any full screen change of the parent page https://github.com/vimeo/player.js/blob/8f371592e8a7998843505de8664c869dfe0d3f1d/src/player.js#L151-L153 I think it needs to be...
This was implemented in #562.
Going to close this since the page linked is now a 404. If you are still seeing playback issues, please [contact support](https://vimeo.com/help/contact).
As far as I know, this is not intentional. For what it's worth, they can still be used as part of the options object, just not as data attributes without...
I'm not sure what options are available to us here. We need to catch the error when running the callbacks, or subsequent ones will not run. I don't think we...
Firefox still does not support the Picture-in-Picture API so our player doesn't know either. If they ever implement that API, it will start working properly through our Player API.
Same host, but not the same origin. If ports are different, it is a different origin. I noticed this because I was testing one project on dev making a request...