Google: We're having to hit pause on Chrome's audio autoplay block

Share

He added that the change wouldn't stop Chrome from silencing most websites' autoplay videos and audio. In response, Google today removed a part of the feature, delaying its launch until later this year.

Other developers have suggested methods for stopping auto-playing audio that would be less disruptive to legacy interactive content, such as automatically muting new tabs or warning the user and offering options when a page first attempts to play audio. When Chrome 66 started rolling out, it was meant to mute annoying ads and videos. Other devs mention that even a notification to let Chrome users know that the browser has automatically muted audio on a webpage would be a welcome change since the original Chrome 66 change automatically mutes audio without any sort of visual indication. It reportedly created problems for artists, as per a report in Waypoint.

As Pallett noted, "We're doing this to give Web Audio API developers (e.g. gaming, audio applications, some RTC features) more time to update their code".

The good news is that Google isn't throwing out the baby with the bath water: Pallett said the change "does not affect most media playback on the web" because the "autoplay policy will remain in effect for video and audio " content.

Macy's Soars on Sales, Earnings Beat
Finally, Schwab Charles Investment Management Inc. raised its position in shares of Macy's by 22.6% in the fourth quarter. Macy's is riding high after pulling off a strong first quarter - keeping up its momentum following robust holiday sales .

The policy will be re-applied to the Web Audio API in the Chrome 70 release this October. This is because their click-to-play approach generally does not resume a Javascript audio interface - something most games never needed to do until Chrome made a decision to press the mute button.

As per a report in The Verge, a developer named Ashley Gullen had revealed the ways to fix the issue, but Pallett has said that it is a "non-trivial user interface challenge".

Google says it is "still exploring options to enable great audio experiences for users", so it may come up with an alternative solution in the future.

The Chrome team admits that it "didn't do a good job of communicating the impact of the new autoplay policy to developers using the Web Audio API". The company said it plans to reintroduce the change with Chrome 70, which is set to debut in October, and that developers should have worked around it by then.

Share