A few days ago Coda told me that the single entry player for non-logged-in users was not working on iPhone. I wasn't certain if this was new, but I'm pretty sure that those players used to work. So I did some research anyways...

https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#webaudio

For Safari on iOS it's been a long known thing that a window/tab will not allow audio to play until there is some form of user interaction. If you open the a playlist player / botb radio in iOS Safari you'll see a big play button which kicks this all off. But now google chrome is apparently adopting this practice for the desktop browser. This breaks audio for countless sites and online html5 games. I am guessing the playlist player / botb radio is working for me because I already have my Media Engagement Index

up to where it needs to be to allow this. I have no idea what anyone else's experience is here, but I'm guessing a fix is necessary. I'll try an incognito window when I get home from work. Also, given that Safari for desktop is built off webkit and chrome develops webkit, more shit is broken.

P.S. -- while working on my VIXXEN20 VIC20 simulation environment and music tracker about 6 weeks ago the graphical display suddenly started taking 4x the CPU it used to. And now this. I have to make a clicky thing instead of it being keyboard only on startup. Fuck this.

can we blame news sites for thinking that autoplay videos on every single page were a good idea

It would seem so. They claim this enhances user experience. One of the comments suggested a better idea where the browser itself says "This site wants to autoplay (audio/video). Is this ok?" like it does for using your mic or webcam or allowing notifications. This shit is so stupid.

Doing anything with audio on mobile in a browser really kinda sucks.
actually, doing webdev for mobile in general really kinda sucks
Desktop Chrome's policy change seems really fucking awful, too.

currently everyone is yelling at google and they responded by reverting and then delaying the same bad decision a few months instead of doing something sensible: https://bugs.chromium.org/p/chromium/issues/detail?id=840866

lmao

This has broken/will break a lot of stuff I work on at my job, and it's pretty cool how instead of actually coming up with a better idea, they're just offloading all the un-fucking on developers.

Good luck with your un-fuck efforts :\

oh guess what?

youtube is allowed to autoplay sound despite these changes!
thanks, google, you fucktards

I'm glad to hear they've reverted the change even if its temporary -- also the rollback didn't include <audio> tags apparently?