ladybird/Tests/LibWeb/Text/input/HTML/HTMLFrameElement-add-remove.html

<!DOCTYPE html>
<head>
    <script src="../include.js"></script>
    <script>
        asyncTest(done => {
            let frameset = document.getElementById("frameset");

            let frame = document.createElement("frame");
            frameset.appendChild(frame);
            frame.remove();

            // Attempting to load the frame will happen in a task on the event loop, so defer completing this test until
            // the event loop has spun once.
            setTimeout(() => {
                println("PASS! (Didn't crash)");
                done();
            })
        });
    </script>
</head>
<frameset id="frameset"></frameset>
Meta: Add DOCTYPEs to most text tests 2025-03-18 19:28:35 +01:00			`<!DOCTYPE html>`
LibWeb: Abort early processing frame/iframe attrs for null navigables We guarded one step against a null navigable, but the very next step also needs to be protected. Let's just abort early instead. This was caught by the following imported WPT test: html/dom/elements/the-innertext-and-outertext-properties/innertext-setter.html This test adds a <frame> element and immediately removes it, but the task to process the src attribute is already queued. Note that <iframe> would have the same issue, but this test does not include them. 2024-11-03 21:30:40 -05:00			`<head>`
			`<script src="../include.js"></script>`
			`<script>`
			`asyncTest(done => {`
			`let frameset = document.getElementById("frameset");`

			`let frame = document.createElement("frame");`
			`frameset.appendChild(frame);`
			`frame.remove();`

			`// Attempting to load the frame will happen in a task on the event loop, so defer completing this test until`
			`// the event loop has spun once.`
			`setTimeout(() => {`
			`println("PASS! (Didn't crash)");`
			`done();`
			`})`
			`});`
			`</script>`
			`</head>`
			`<frameset id="frameset"></frameset>`