Windows 10 News and info | Forum
January 21, 2019, Loading... *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: This is a clean Ad-free Forum and protected by StopForumSpam, Project Honeypot, Botscout and AbuseIPDB | This forum does not use audio ads, popups, or other annoyances. New member registration currently disabled.
  Website   Home   Windows 8 Website GDPR Help Login Register  
By continuing to use the site or forum, you agree to the use of cookies, find out more by reading our GDPR policy.
Pages: [1]
Share this topic on Del.icio.usShare this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on MySpaceShare this topic on RedditShare this topic on StumbleUponShare this topic on TechnoratiShare this topic on TwitterShare this topic on YahooShare this topic on Google buzz
Author Topic: Chrome's new autoplay requirements are breaking online games  (Read 73 times)
Hero Member
Offline Offline

Gender: Male
United States United States

Posts: 29460

I Do Windows

WWW Email
« on: May 13, 2018, 04:41:20 PM »

For years, autoplay video and audio on the web have been a constant source of frustration for users. Restrictions on autoplay content have been in mobile browsers for years, partially due to the processing limitations of early smartphones, and partially to conserve mobile data usage. With the release of Chrome 66 late last month, Google introduced new autoplay restrictions on both mobile and desktop Chrome.

While most users (myself included) celebrated this change, there has been plenty of valid criticism. The new policy has significantly affected game developers, many of whom say their games are now broken on Chrome. One developer wrote in a tweet, "the way which people engage with these pages differs in such a way that an autoplay policy designed for text articles with embedded video may not be appropriate."

The critism is mostly focused on Google's 'Media Engagement Index,' which is how Chrome determines if the page is allowed to automatically play media. This is an algorithm that takes several factors into account, including how long media is consumed, if the tab is active, and how large the video element is. As such, it's difficult for developers to test how their pages function for all users.

In the above tweet, one developer noted that simply using the Chrome Dev Tools (a panel often used while testing pages) counted as user interaction, thus making it difficult to replicate the block and diagnose its effects. Other developers have chimed in with further criticism.

Google appears open to reversing the change, or at least adapting it to fix web games. The Chrome team has asked developers to submit sites that broke after the policy change, but the discussion about reversing the change has been made private.

In the meantime, Google recommends using the newer WebAudio API, which is not subject to the same limitations. However, this requires rewriting existing games that use normal HTM5 audio and video.


Pages: [1]
Jump to:  

Powered by SMF 1.1.21 | SMF © 2017, Simple Machines

Google visited last this page November 14, 2018, 08:56:56 AM