Browser Permission Policies seem to have changed.

[efi]

Hi!

In Google Chrome 78.0.3904.70 on Windows 10 (with Seaboard Block connected through BLE via MIDIBerry and Midi Loopback Device, but that should not matter) I recieve error messages instead of a working page:

script.js?v1.0.0:53 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
(anonymous) @ script.js?v1.0.0:53

script.js?v1.0.0:388 [Deprecation] Web MIDI will ask a permission to use even if the sysex is not specified in the MIDIOptions since M77, around September 2019. See https://www.chromestatus.com/feature/5138066234671104 for more details.
init @ script.js?v1.0.0:388

Maybe that means only a few changes to the code?

[espoelstra]

I've been able to work around this locally by adding a Promise or async/await that waits for a "click" by the user on the page before trying to load the MpePlayer.init and re-initalizing the AudioContext.

The weird thing I'm running into is that the Seaboard or Lightpad block images never actually show up on the page even after I've connected them, but running with Debug allows me to see the notes being pressed.

[manifestinteractive]

Man, I have no idea how I missed this issue getting reported. I will take a look at what is going on here. Seems like Chrome just added a security measure to require user interaction first, so might need to swap out the library to add hooks for engagement.