ladybird/Tests/LibWeb/Text/input/html-parser-text-in-table-hoisting.html

<!DOCTYPE html>
<script src="include.js"></script>
<body><table><tr>PASS</tr></table></body>
<script>
    test(() => {
        // Remove the table. "PASS" should still be visible,
        // as the HTML parser inserts it *before* the table
        // under these circumstances.
        document.querySelector("table").remove()
        println(document.body.innerText);
    });
</script>
Meta: Add DOCTYPEs to most text tests 2025-03-18 19:28:35 +01:00			`<!DOCTYPE html>`
LibWeb: Make HTML parser flush all pending tokens in "in table text" There were multiple bugs in the parsing algorithm for handling text occurring inside a `table` element: - When there was pending non-whitespace text inside a table, we only flushed one token instead of all pending tokens. - Also, we didn't even flush one of the right tokens, but instead the token that caused the flush to happen. - Once we started flushing the right tokens, it turned out we had not yet implemented character insertion points expressed as "before X". - Finally, we were not exiting the "in table text" mode after flushing pending tokens, effectively getting us stuck in that mode until EOF. 2023-07-03 10:00:20 +02:00			`<script src="include.js"></script>`
			`<body><table><tr>PASS</tr></table></body>`
			`<script>`
			`test(() => {`
			`// Remove the table. "PASS" should still be visible,`
			`// as the HTML parser inserts it before the table`
			`// under these circumstances.`
			`document.querySelector("table").remove()`
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 12:38:10 -04:00			`println(document.body.innerText);`
LibWeb: Make HTML parser flush all pending tokens in "in table text" There were multiple bugs in the parsing algorithm for handling text occurring inside a `table` element: - When there was pending non-whitespace text inside a table, we only flushed one token instead of all pending tokens. - Also, we didn't even flush one of the right tokens, but instead the token that caused the flush to happen. - Once we started flushing the right tokens, it turned out we had not yet implemented character insertion points expressed as "before X". - Finally, we were not exiting the "in table text" mode after flushing pending tokens, effectively getting us stuck in that mode until EOF. 2023-07-03 10:00:20 +02:00			`});`
			`</script>`