ladybird/Tests/LibWeb/Text/input/input-readonly.html

<!DOCTYPE html>
<input id=input type=text readonly><script src="include.js"></script><script>
    test(() => {
        const input = document.getElementById("input");
        internals.sendText(input, "wfh :^)");
        internals.commitText();

        println(input.value);
    });
</script>
Meta: Add DOCTYPEs to most text tests 2025-03-18 19:28:35 +01:00			`<!DOCTYPE html>`
LibWeb: Add textarea readonly support 2024-02-26 19:12:32 +01:00			`<input id=input type=text readonly><script src="include.js"></script><script>`
			`test(() => {`
			`const input = document.getElementById("input");`
			`internals.sendText(input, "wfh :^)");`
			`internals.commitText();`
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(input.value);`
LibWeb: Add textarea readonly support 2024-02-26 19:12:32 +01:00			`});`
			`</script>`