3 ms·
Ironically that google link seems to be broken in Chrome, because it predates the time in 2018 when chrome intentionally broke most/all existing webaudio conten
by fenomas 6y ago
Ironically that google link seems to be broken in Chrome, because it predates the time in 2018 when chrome intentionally broke most/all existing webaudio content.
(Ostensibly the change was meant to prevent pages from auto-playing sounds without user input, but in practice it broke pages regardless of whether they did so.)
Details: https://developers.google.com/web/updates/2018/11/web-audio-autoplay https://developers.google.com/web/updates/2018/11/web-audio-...
- gfxgirl 6y agoStrange, that google one works for me in Chrome and it was made after the restrictions The more embarrassing one for Google is this entire site https://www.google.com/search?q=link%3Ahttps%3A%2F%2Fmusiclab.chromeexperiments.com%2F https://www.google.com/search?q=link%3Ahttps%3A%2F%2Fmusicla...
- fenomas 6y agoIt's unpredictable; the chrome policy that breaks webaudio is partly based on your browsing behavior. When they first applied the policy (mid 2018), it broke pretty much all webaudio and they un-applied it a few days later. When they later reapplied it (late 2018) they didn't change the policy itself, but apparently added a thing where chrome ignores the policy if it remembers you having allowed audio to play at that site before. Anyhoo it looks like I was in an incognito tab when I tried it before and the audiocontext was silenced. In a regular tab it plays normally (for me, anyway).
- moron4hire 6y agoWhat's really weird is that sometimes the audio works of you navigated to the page, but if you refresh the page it breaks. For as much as Google engineers talk about "don't break the Web", they break the fucking web all the time.