What is, erroneously, this update completely eliminates the audio features of interactive Web projects that depend on specific commands, which obviously poses a big problem for artists (muting all projects into mutes).
Google Product ManagerJohn PallettSaid:
The team is working hard to improve users andDevelopmentThe work of the staff, but this time failed to communicate the impact of the changed automatic play strategy to the developers.
As a remedy, Google did not completely roll back the ability to block auto-play elements in Chrome 66. Instead, Google restricted the use of Web Audio APIs by application developers while maintaining regular audio.videoAutomatic playback integrity.
Of course, this is not a permanent measure. Pallett claims:
Relevant restrictions will return in Chrome 70, released in October this year, so developers are still urged to follow Google's guidelines to modify their code.
For Pallett's explanation, many online audio tools were developedBenji KayDo not buy it.He criticized: "The mere delay of this policy does not fundamentally solve the content problem."
Another developer, Ashley Gullen, had previously proposed to solve the problem.One suggestion, but Pallett called this "a major UI challenge" that the company is still inspecting:
We are still exploring options to provide users with an excellent audio experience, and we will publish more detailed ideas on this topic later.
For developers, this is not a victory, because Google has not made any commitment to solve the core issues in the update. Even delaying the issue until October will still put some pressure on game makers and the Chrome team.