Skip to content

Chrome 66 will break audio init

Chrome 66 is scheduled to require a user interaction before audio can start.

This works in a page:

if (window.confirm("Turn on maxiLib audio?")) {
    maxiAudio.init();
}

See: https://live.codecircle.com/d/Mc9uWNu22EBpD2sq6

Unfortunately, adding the dialog to maxiLib itself doesn't seem to have been enough. I'm not sure if the Chrome Canary I'm using is exhibiting the final behaviour, though.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information