Player.js: Cross-Origin Read Blocking (CORB) blocked cross-origin response

[oguilleux]

I'm initialising a player like so :

// HTML
<iframe
  class="home__hero__video"
  src="https://player.vimeo.com/video/MYVIDEOIDHERE?background=1&autoplay=0&loop=1&byline=0&title=0"
  frameborder="0"
  webkitallowfullscreen
  mozallowfullscreen
  allowfullscreen>
</iframe>

// JS - webpack + babel
import Player from '@vimeo/player';
class HomeFn {
  constructor() {
    this.initVideo();
  }

  initVideo() {
    const player = new Player(document.querySelector('.home__hero__video'));
    player.on('loaded', () => {
      player.play();
    });
  }
}
export default HomeFn;

And I get this warning in my console :

Cross-Origin Read Blocking (CORB) blocked cross-origin response https://fresnel.vimeocdn.com/add/player-stats?session-id=6382900865a72ab0f6813cecc33d0ebc654a744d1556634198 with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details.

How can I solve this console warning ? Thanks for your help.

[luwes]

hi @oguilleux, thanks for reporting.

we're currently working to hide this warning however it shouldn't affect website behavior, it can safely be ignored for the time being.

For more info see https://www.chromium.org/Home/chromium-security/corb-for-developers.

[oguilleux]

Ok, thanks for your quick feedback.

[munyah]

Hi guys,

This is actually breaking website behaviour on my sites; is there a patch or something that one could use in the meantime?

[jstortz]

Hi guys,

This is actually breaking website behaviour on my sites; is there a patch or something that one could use in the meantime?

how is it breaking the site? Asking as I'm curious. I get the warning, but it doesn't seem to be breaking anything...but your comment makes me wonder if I'm missing something.

[munyah]

@jstortz My site makes use of a carousel that contains multiple vimeo videos. For every instance that is blocked CORB; the body response is empty & as such will not load the videos altogether.

The CORB documentation quoted above by @luwes does state that CORB may replace the body with an empty response in some scenarios.

[anchietajunior]

Hello guys,

In my app (staging and production) the videos just stoped playing when i get this warning, localhost is working fine, any ideas?

---

Well, a little update, my problem is solved, i just removed the iframe and let javascript take over everything. Now my videos are playing normally.

[mozzi]

Sorry, my fail. on this website we don't use player.js, we use default vimeo player, so probably we will submit this bug to support after some investigation. I'll keep screenshot here, maybe it will help you somehow.
Same here. On one of the company computers video just stopped working. chrome version 74.0.3729.157. Tried on multiple other computers with same chrome version - wasn't able to reproduce.
Os Mojave 10.14

Screenshot

[luwes]

Could you please send the OS/browser and the link of affected videos?

It really shouldn't affect playback at all because it's only blocking a request to the analytics.

[luwes]

Oh I see it's in the screenshot :) for you @mozzi. Will check it out.

[mozzi]

sorry, my mistake. on this website we use default vimeo player, not player.js. i've updated comment.

[nikolovag]

I also get this warning in the console and it actually breaks my website. Can't load facebook videos and not supported MIME type is text/html