ladybird/Tests/LibWeb/Text/input/Editing/input-into-empty-contenteditable.html

<!DOCTYPE html>
<script src="../include.js"></script>
<style>
    #input {
        width: 100px;
        height: 100px;
        border: 1px solid black;
    }
</style>
<div id="input" contenteditable="true"></div>
<script>
    test(() => {
        const input = document.getElementById("input");
        internals.sendText(input, "hello");
        println(document.body.innerText);
    });
</script>
Meta: Add DOCTYPEs to most text tests 2025-03-18 15:28:35 -03:00			`<!DOCTYPE html>`
LibWeb: Fix crashing after input into empty contenteditable Change `EventHandler::handle_keydown()` to no longer assume the cursor position's node is always a `DOM::Text`. While this assumption holds for `HTMLInputElement` that has a shadow DOM with a text node, an empty `contenteditable` might not have any children. With this change, `handle_keydown()` creates a new text node if the cursor position's node is not a text node. 2024-02-23 22:53:35 -03:00			`<script src="../include.js"></script>`
			`<style>`
			`#input {`
			`width: 100px;`
			`height: 100px;`
			`border: 1px solid black;`
			`}`
			`</style>`
			`<div id="input" contenteditable="true"></div>`
			`<script>`
			`test(() => {`
			`const input = document.getElementById("input");`
			`internals.sendText(input, "hello");`
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			`println(document.body.innerText);`
LibWeb: Fix crashing after input into empty contenteditable Change `EventHandler::handle_keydown()` to no longer assume the cursor position's node is always a `DOM::Text`. While this assumption holds for `HTMLInputElement` that has a shadow DOM with a text node, an empty `contenteditable` might not have any children. With this change, `handle_keydown()` creates a new text node if the cursor position's node is not a text node. 2024-02-23 22:53:35 -03:00			`});`
			`</script>`