One, who also commented on the issue on the Chromium page, pointed out that most work won’t be update by October, if its ever updated at all. Under 'Automute preferences,' you can choose to only play. However, some developers are still upset. Click the wrench icon in the top right of the Chrome window, then select 'Tools,' then 'Extensions,' then click 'Options' next to MuteTab. This should restore sound to sites affected by the new auto-mute feature. Google is experimenting on fixing this thanks to a new update to Google Chrome’s Canary development build allowing you to mute/unmute tabs indefinitely for a specific site. “The team here is working hard to improve things for users and developers, but in this case we didn’t do a good job of communicating the impact of the new autoplay policy to developers using the Web Audio API.” gaming, audio applications, some RTC features) more time to update their code,” said Google Chrome product manager John Pallett, in a comment on the issue page. “We’re doing this to give Web Audio API developers (e.g. Now, automatic mute won’t apply to anything using the Web Audio API until Chrome 70, which scheduled for release in October. ![]() The issue is with the Web Audio API, says Google. ![]() ![]() We use these channels to slowly roll out updates to users, starting with our close to daily Canary channel builds, all the way up to our Stable channel releases that happen every 6 weeks roughly. The team is pushing out a new version of Chrome 66 (version. Chrome supports a number of different release channels. Google is partially disabling Chrome’s fancy auto-mute feature after it silenced some web games and art projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |