gecko-dev/dom/media/webaudio/test/test_scriptProcessorNodeNotConnected.html
Ehsan Akhgari 09a262787c Bug 649012 - Fail mochitest-plains which use flaky timeouts (setTimeout(x) for x > 0); r=ted
We are white-listing the existing set of tests that use setTimeout
like this.  Hopefully these tests will be investigated and fixed
in the future, so that we can narrow down the white-list.

This check is only turned on for mochitest-plain for now.
2014-12-11 13:34:40 -05:00

35 lines
1.1 KiB
HTML

<!DOCTYPE HTML>
<html>
<head>
<title>Test AudioBufferSourceNode: should not fire audioprocess if not connected.</title>
<script type="text/javascript" src="/tests/SimpleTest/SimpleTest.js"></script>
<script type="text/javascript" src="webaudio.js"></script>
<link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css" />
</head>
<body>
<pre id="test">
<script class="testbody" type="text/javascript">
SimpleTest.waitForExplicitFinish();
SimpleTest.requestFlakyTimeout("This test needs to wait a while to ensure that a given event does not happen.");
addLoadEvent(function() {
var context = new AudioContext();
var sp = context.createScriptProcessor(2048, 2, 2);
sp.onaudioprocess = function(e) {
ok(false, "Should not call onaudioprocess if the node is not connected.");
sp.onaudioprocess = null;
SimpleTest.finish();
};
setTimeout(function() {
console.log(sp.onaudioprocess);
if (sp.onaudioprocess) {
ok(true, "onaudioprocess not fired.");
SimpleTest.finish();
}
}, 4000);
});
</script>
</pre>
</body>
</html>