webMUSHRA doesn't work correctly on Chrome >= 70

[faroit]

Lets have this in mind and check if we are affected:
https://bugs.chromium.org/p/chromium/issues/detail?id=807017

[faroit]

version 66 is now in the Dev channel. Can someone test it using chrome 66? @mschoeffler @aladami

[faroit]

Chrome 66 was released and I just checked: webMUSHRA is affected by this change.
In clear text: webMUSHRA does not work anymore with Chrome!

@mschoeffler do you have time to fix it?
If not, I would propose to either put a warning in the readme or deprecate webMUSHRA entirely.

[faroit]

@mschoeffler I've added a warning on the readme.md. 88b6c89

[faroit]

ping @mschoeffler

[faroit]

I don't know what exactly has changed in Chrome but it works fine now in 66.0.3359.139

[faroit]

stopped working again in Chrome 66.0.3359.170...

@mschoeffler

[faroit]

Note: The Web Audio API will be included in the Chrome autoplay policy with M70 (October 2018).

new autoplay policy will break webmushra again

[faroit]

The Web Audio API will be included in the Chrome autoplay policy with M71 (December 2018).

we need to address this soon

[lgestin]

Adding

document.addEventListener("click", function() {
    if (audioContext.state !== 'running') {
        audioContext.resume();
    }
}, true);

in startup.js fixes the issue for me.

[faroit]

@lgestin looks like a working workaround, thanks. Can you add a PR?

[faroit]

@lgestin in case this is still a recommended workaround, can you open a PR for this fix?