For example, sound on many audio apps and other interactive experiences no longer plays, with developers required to update many sites.
Have you come across any such unintended consequences on Chrome?
The Chromium team confirms: "We've updated Chrome 66 to temporarily remove the autoplay policy for the Web Audio API". "If you are honest in your claim that the side effects of the policy were unintended and unwanted, you should commit-in clear, straightforward language-to finding other alternatives which do not break vast swathes of cultural work that was developed and distributed on the open web".
Meanwhile, the implementation delay is created to give "Web Audio API developers (e.g. gaming, audio applications, some RTC features) more time to update their code". "The team here is working hard to improve things for users and developers", he said, "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".
The autoplay-video blocker is created to fix one of the greatest problems of the Internet: autoplaying videos on websites. 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.
Still, the auto-muting update still appliesto audio and video HTML tags.
Some have pointed out that sound is broken even on sites that are silent until the user hits a play button. However, the more you use Chrome, the better the browser becomes at understanding your personal do's and don't's, and will make adjustments accordingly.
Chrome 66 introduced a new autoplay policy that prevented audio and video from automatically playing in a browser tab.
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.