2

TLDR; How do I enable the autoplay-policy flag in >= Chrome 62? The autoplay problem has been thoroughly discussed, but in this question I want to edit the settings for my own browser to run a browser extension game that can play its own sounds in a "kiosk".

Issue; I am building a chrome extension that plays a game on top of web pages. I am now creating the demo mode that automatically goes to new urls and launches the game so viewers can watch it in galleries, etc. However, because this is an automated script (users watch it passively) and these web pages are random (so do not have a high Media Engagement Index (MEI) chrome://media-engagement/) my extension sounds are suspended chrome://media-internals/:

suspended

I have looked at:

  • Javascript but their policy says a user has to interact with the domain (which is not possible)
  • Increasing the domain's MEI score (again, not possible)
  • Setting the "Developer Switch" at chrome://flags/#autoplay-policy to allow autoplay (but it seems this page no longer works as of at least Chrome 76).

Picture of game for context:

enter image description here

ow3n
  • 5,974
  • 4
  • 53
  • 51

1 Answers1

1

I temporarily "solved" this by using Chrome Canary v78 with start up flags found in this SO question description. In Terminal (Mac)...

/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary  --autoplay-policy=no-user-gesture-required
ow3n
  • 5,974
  • 4
  • 53
  • 51
  • 1
    this works even for non-canary versions of chrome, and is officially documented here: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes – Hoff Sep 18 '20 at 21:03