AudioContext.decodeAudioData returns a Promise

LayoutTests/webaudio/decode-audio-data-basic-expected.txt

Index: LayoutTests/webaudio/decode-audio-data-basic-expected.txt
diff --git a/LayoutTests/webaudio/decode-audio-data-basic-expected.txt b/LayoutTests/webaudio/decode-audio-data-basic-expected.txt
index 9b5a6282f04ec86c1d7778814a54f5187d5fc057..aff5acf566e2fa63e924b9be3d15f646f3281ba1 100644
--- a/LayoutTests/webaudio/decode-audio-data-basic-expected.txt
+++ b/LayoutTests/webaudio/decode-audio-data-basic-expected.txt
@@ -1,9 +1,10 @@
+CONSOLE ERROR: line 21: Uncaught (in promise) NotSupportedError: invalid ArrayBuffer for audioData.

[hongchan, 2015/03/23 16:18:49]

We don't want this kind of error messages in the expected result. Do we?

[Raymond Toy, 2015/03/23 18:45:20]

I'm undecided.  I kind of didn't want to write decodeAudioData().then(), because
it's not required, even if promises are supported. But it's also annoying to
have that in the expected result.

 Basic tests for decodeAudioData function.
 
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
 
 
-PASS decodeAudioData raises exception correctly when arraybuffer parameter is null.
+PASS decodeAudioData(null) invoked errorCallback correctly.
 PASS The resources/media/24bit-44khz.wav test: successCallback has been called correctly.
 PASS The resources/media/invalid-audio-file.txt test: errorCallback has been called correctly.
 PASS successfullyParsed is true