0

The Google Chrome latest version 66.0.3359.139 (April 26, 2018) does not allow to autostart not muted Youtube Videos, now like in Android or iOS. I'm not sure at all if the problem is the new Google Chrome version os a new Youtube API version or policy, but I can't find any changes made on it. I saw the problem in an application running in Mac and in ChromeOS (Chromebit) with the iframe embed player with javascript API enabled.

Has somebody information? Can it be an issue, or a new security or performance policy?

EDIT:

It does not happen always but almost.

EDIT 2: Certainly I got this error trying tu put in mute and unmute with a setTimeout of 4000 ms and I've got the error: "Unmuting failed and the element was paused instead because the user didn't interact with the document before"

But why now?

Thanks!

Luis Gar
  • 457
  • 1
  • 4
  • 18
  • 2
    To check on the new policy changes, you can refer in the documentation specifically on the [Autoplay Policy Changes(https://developers.google.com/web/updates/2017/09/autoplay-policy-changes). This changes was also mentioned in [this blog](https://www.digitaltrends.com/computing/google-chrome-66-to-start-blocking-auto-play-video/). – MαπμQμαπkγVπ.0 May 07 '18 at 10:46

2 Answers2

2

Muted autoplay is always allowed.

So we can append mute=1 to the video link.

for eg: https://www.youtube.com/embed/VIDEO_ID?playlist=VIDEO_ID&autoplay=1&mute=1&loop=1&rel=0

Hope this will help for someone looking for autoplay. This example will autoplay the video continuously and hide relative video pop up box.

user3575353
  • 397
  • 1
  • 8
0

This question asking for the same I am is better explained:

How to allow video autoplay in a Google Chrome kiosk app in version 66 or later

EDIT: Is new policy from chrome 66 as said in the link pasted in the comment Thank you

EDIT II: The answer in the threat mentioned works: https://stackoverflow.com/a/50222347/5154908

Luis Gar
  • 457
  • 1
  • 4
  • 18