When Google updated Chrome to automatically block autoplay videos last week, it was seen as a victory for internet-goers who long endured annoying advertisements. But what most people didn’t consider is how the changes would affect other content. It now appears the Chrome 66 update has had some unintended consequences that threaten web-based games.
Prior to the update, game audio would either start when a webpage loaded, or more commonly, after the user pressed “play.” With the latest version of Chrome, games created using any HTML5 engine — Pico-8, GameMaker, Unity, or Phaser — don’t play sound. In many cases, audio won’t even play even when a game requires users to “click to play.”
Read more at: The Daily Dot.
HTML5 Game Developer, Enclave Games indie studio founder, js13kGames competition creator and Gamedev.js Weekly newsletter publisher. Mozilla Tech Speaker, Gamedev.js community firestarter. Organizes meetups / workshops / hackathons in Poland, passionate about new, Open Web technologies, excited about WebXR and PWAs. Likes eating sushi and playing Neuroshima Hex.
