Revision 6dafebae502632ba0009440dc254ce6b9a10e84e authored by Mike Pennisi on 27 March 2018, 00:09:16 UTC, committed by Mike Pennisi on 27 March 2018, 00:45:48 UTC
Because a harness error may describe an unrecoverable browser state, the browser should always be restarted when such an error is encountered (even in the presence of the `--no-restart-on-unexpected` flag).
1 parent f497de8
WorkerGlobalScope_ErrorEvent_filename.htm
<!DOCTYPE html>
<title> WorkerGlobalScope onerror event handler argument: location </title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<div id=log></div>
<script>
// The worker events races with the window's load event; if the worker events
// arrive first, the harness will detect the error event and fail the test.
setup({ allow_uncaught_exception: true });
async_test(function(t) {
var worker = new Worker('./support/ErrorEvent.js');
worker.onmessage = t.step_func_done(function(e) {
var href = location.href;
var expected = href.substring(0, href.lastIndexOf('/')) + '/support/ErrorEvent.js';
assert_equals(e.data.filename, expected);
});
worker.postMessage("Error Message");
});
</script>
Computing file changes ...
