For that reason, the current Chrome version 66 will no longer automatically mute Web Audio objects. This further resulted in the company receiving numerous complaints regarding the new feature.
The feature is reportedly barring apps and interactive art from playing audio notifications and other elements. But it's having the unexpected effect of stopping web apps and games from playing audio, much to the annoyance of developers.
Other comments call for a response from the Chrome development team, particularly with regard to suggestions for modifying the policy to indicate when audio is being disabled, and to enable users to easily switch it back on, either temporarily or permanently.
Google released yesterday a Chrome update that temporarily fixed a bug that broke millions of web-based games, some of which couldn't play audio at all, despite whatever tricks and configs users tried.
The Chrome team said that the changes will not impact the web browser's new feature of silencing Internet videos and audio that have an autoplay feature.More news: Guatemala Inaugurates Embassy In Jerusalem After US
More news: Watch Ronda Rousey In New Trailer for Her Upcoming Movie 'Mile 22'
More news: Shining Sonam Kapoor At Cannes
Google says the policy will once again be applied to the Web Audio API in October, and that developers have until that point to update the code in their web-based games and apps according to Google's developer guidelines. Some feel that Google is restricting the spirit of a free and open web buy forcing their standards on the world's most popular browser.
While the original audio policy change blindsided developers, the temporary rollback seeks to give them time to adapt their projects for the coming change but, as some devs pointed out last week, not everyone affected by the change has the ability, time, or resources to go back and retroactively change the code of projects already online. This shouldn't affect most audio and videos (included in the audio and video HTML tags), which will continue to be auto-muted, but should ensure the accidentally affected web components are working correctly.
These challenges relate to how to obtain a gesture from users from different types of web applications.
The autoplay blocking is an example of how browsers are getting more assertive on behalf of users faced with pushy websites.