mentioned here
yeah sure nice side effects
eg. look at all those websites user experience destroyed by Chrome
So in this bug report
Issue 840866 - Allow audio to autoplay, but optionally mute output
we can see other articles talking about that bug
In blocking autoplay videos, Chrome is breaking many Web-based games
WebAudio change means HTML5 games won't work without developer action.
An update Google rolled out for its popular Chrome browser this weekend helps prevent those annoying auto-playing video ads on many websites from disturbing your day with unwanted sound as well. But that update is causing consternation for many Web-based game developers who are finding that the change completely breaks the audio in their online work.
The technical details behind the problem involve the way Chrome handles WebAudio objects, which are now automatically paused when a webpage starts up, stymying auto-playing ads. To get around this, Web-based games now have to actively restart that pre-loaded audio object when the player makes an action to start the game, even if that audio wasn't autoplaying beforehand. "The standard doesn't require you to do this, so no one would have thought to do this before today," developer Andi McClure told Ars Technica.
...
wait ... did they not spent a lot of efforts to kill Flash to avoid such kind of things?
they did (I'm talking about Google alright)
and it seems that is not as simple a problem they thought it would be
eg. How can we block bad/abusive content and at the same time allow good content ?
and this time they can not blame a plugin like Flash for the problem
but it does show a much bigger problem:
Should users let the browser vendor decide for them what content they are allowed to consume ?
The same way I find abusive to force-block the Flash player plugin
I also find abusive to block sound on a web page
and yeah I do hate ads and autoplay video ads in particular
here more details
... This stealth change doesn't seem to have been heavily promoted by Google, forcing game developers to pay constant and precise attention to Google's documentation to see it coming.
Most developers didn't, leading to widespread complaints from Web-based developers big and small that their games are suddenly not working in Chrome. Meanwhile, content on what Google says are "over 1,000 sites where the highest percentage of visitors play media with sound" (such as, ahem, Google's own YouTube) are being automatically whitelisted to avoid these disruptive changes.
is that not beautiful ?
first advice: change browser
really that is hilarious
second comment even better
and another comment show how it does not affect Google's content
Voila what happen when the browser want to decide for you of what is allowed or not
I continue to say it's not that everyone was hating Flash, it was everyone hated ads (and still do)
and my take on all that is that ultimately users should be king in deciding which/what/where content is allowed
that is called the user experience, something Google seems to not care about
and something Flash was very good at.