ladybird/Tests/LibWeb/Text/input/scripted-dom-insertion-during-html-parse.html

<!DOCTYPE html>
<body></body>
<script src="include.js"></script>
<script>
    document.body.appendChild(document.createTextNode("PASS"));
    test(() => {
        println(document.body.innerText);
    });
</script>
Meta: Add DOCTYPEs to most text tests 2025-03-18 15:28:35 -03:00			`<!DOCTYPE html>`
LibWeb: Don't overwrite existing text content when flushing HTML parser If we run an inline script from the HTML parser, it may append a text node to the current insertion point. If there was text content immediately following the script element, we would previously overwrite the script-inserted text content, due to an oversight in the way we select an appropriate insertion point This patch fixes the issue by only inserting parser content into existing text nodes if they are empty. 2023-08-16 05:58:12 -03:00			`<body></body>`
LibWeb+WebContent+headless-browser: Support async text tests Previously, we used `on_load_finish` to determine when the text test was completed. This method did not allow testing of async functions because there was no way to indicate that the runner should wait for the async call to end. This change introduces a function in the `internals` object that is intended to be called when the text test execution is completed. The text test runner will now ignore `on_load_finish` which means a test will timeout if this new function is never called. `test(f)` function in `include.js` has been modified to automatically terminate a test once `load` event is fired on `window`. new `asyncTest(f)` function has been introduces. `f` receives function that will terminate a test as a first argument. Every test is expected to call either `test()` or `asyncTest()` to complete. If not, it will remain hanging until a timeout occurs. 2023-09-14 14:17:32 -03:00			`<script src="include.js"></script>`
LibWeb: Don't overwrite existing text content when flushing HTML parser If we run an inline script from the HTML parser, it may append a text node to the current insertion point. If there was text content immediately following the script element, we would previously overwrite the script-inserted text content, due to an oversight in the way we select an appropriate insertion point This patch fixes the issue by only inserting parser content into existing text nodes if they are empty. 2023-08-16 05:58:12 -03:00			`<script>`
			`document.body.appendChild(document.createTextNode("PASS"));`
LibWeb+WebContent: Do not include DOM HTML in text test expectations For example, in the following abbreviated test HTML: <span>some text</span> <script>println("whf")</script> We would have to craft the expectation file to include the "some text" segment, usually with some leading whitespace. This is a bit annoying, and makes it difficult to manually craft expectation files. So instead of comparing the expectation against the entire DOM inner text, we now send the inner text of just the <pre> element containing the test output when we invoke `internals.signalTextTestIsDone`. 2024-10-02 13:38:10 -03:00			`test(() => {`
			`println(document.body.innerText);`
			`});`
LibWeb: Don't overwrite existing text content when flushing HTML parser If we run an inline script from the HTML parser, it may append a text node to the current insertion point. If there was text content immediately following the script element, we would previously overwrite the script-inserted text content, due to an oversight in the way we select an appropriate insertion point This patch fixes the issue by only inserting parser content into existing text nodes if they are empty. 2023-08-16 05:58:12 -03:00			`</script>`