ladybird/Tests/LibWeb/Text/input/HTML/Window-onerror.html

<!DOCTYPE html>
<script src="../include.js"></script>
<script>
    asyncTest(done => {

        removeTestErrorHandler()

        window.addEventListener("error", (event) => {
            println(`onerror event fired: ${event.error}`);
            done();
        });

        try {
            throw new Error("FAIL");
        } catch (e) {}

        throw new Error("Uncaught error");
    });
</script>
LibWeb: Fire error event when script has an execution error We now use the "report an exception" AO when a script has an execution error. This has mostly replaced the older "report the exception" AO in various specifications. Using this newer AO ensures that `window.onerror` is invoked when a script has an execution error. 2024-09-26 15:40:23 +01:00			`<!DOCTYPE html>`
			`<script src="../include.js"></script>`
			`<script>`
			`asyncTest(done => {`
LibWeb: Add a feature to LibWeb tests to fail on unhandled exceptions Previously, if there was an unhandled exception in an async test, it might fail to call done() and timeout. Now we have a default "error" handler to catch unhandled exceptions and fail the test. A few tests want to actually test the behavior of window.onerror, so they need an escape hatch. 2024-10-04 16:11:00 -06:00
			`removeTestErrorHandler()`

LibWeb: Fire error event when script has an execution error We now use the "report an exception" AO when a script has an execution error. This has mostly replaced the older "report the exception" AO in various specifications. Using this newer AO ensures that `window.onerror` is invoked when a script has an execution error. 2024-09-26 15:40:23 +01:00			`window.addEventListener("error", (event) => {`
			println(`onerror event fired: ${event.error}`);
			`done();`
			`});`

			`try {`
			`throw new Error("FAIL");`
			`} catch (e) {}`

			`throw new Error("Uncaught error");`
			`});`
			`</script>`