Pallett said that the change will not affect Chrome’s silencing of most autoplaying video and audio on the web. “Come October, any existing software which utilises sound and which is not or cannot be any longer maintained will be broken.” Benji Kay, a developer of web games and audio tools, said: “Simply delaying the enacting of this policy doesn’t solve any of the major concerns that have been raised. The change was greeted with scepticism by developers. The policy will be reapplied to the Web Audio API in Chrome 70 (October).” “We’re doing this to give Web Audio API developers (eg gaming, audio applications, some RTC features) more time to update their code. One of Google’s project managers for Chrome, John Pallett, said: “We’ve updated Chrome 66 to temporarily remove the autoplay policy for the Web Audio API. But the update also broke a series of apps, games and interactive art in the process, preventing them from playing audio for alerts and other elements, and causing complaints from developers and users of these interactive web apps.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |