feat: add legacy decodeAudioData signature

[b-ma]

First step regarding #57

"get rid of the wpt fork (how to deal with webaudio/resources/buffer-loader.js)"

[b-ma]

Ok, I just added a mock for the XMLHttpRequest in .scripts/wpt-mock/, should allow to fix the second step.

You can test it by running:

node ./.scripts/wpt-mock/wpt-buffer-loader.js

[orottier]

Hah pretty cool. To be fair I had not noticed yet that we need this machinery.

The issue I was referring to was the problem that we need a cp wpt/webaudio/js/buffer-loader.js wpt/webaudio/resources in order for the wpt-runner to not crash. That is still something to be addressed (probably by rebuilding the statis assets of the wpt-runner repo - I need to look into this further).

The cool thing is that you now have probably solved some failed tests because of the missing XMLHttpRequest :)

[orottier]

Hm the issue may just be inside the wpt repo:
https://github.com/web-platform-tests/wpt/blob/0c8c0662ed5d444bf12992e433502e8b6af640d4/webaudio/the-audio-api/the-audiobuffersourcenode-interface/sample-accurate-scheduling.html#L15

refers to the non-existing file

[b-ma]

Hum weird indeed... This looks like an issue in the wpt repo indeed, the path in another file is right https://github.com/web-platform-tests/wpt/blob/0c8c0662ed5d444bf12992e433502e8b6af640d4/webaudio/the-audio-api/the-mediaelementaudiosourcenode-interface/mediaElementAudioSourceToScriptProcessorTest.html#L20

And in the file you pointed to, the BufferLoader is not even used... I guess in a browser it just triggers a 404 error with no harm, so they didn't noticed

As a temporary solution, we could just copy the file in the resources directory using npm scripts (should be very simple) and ignore changes in the wpt submodule (e.g. https://medium.com/@maryam.ghani160/how-to-ignore-changes-in-git-submodules-a3ea1463bdde), what do you think?