ladybird/Tests/LibWeb/Text/input/DOM/Range-to-string.html

<!DOCTYPE html>
<body><p id="p1"><b>Hello💨</b>😮 World</p>
<script src="../include.js"></script>
<script>
    test(() => {
        const p1 = document.getElementById("p1");
        const hello = p1.firstChild.firstChild;
        const world = p1.lastChild;
        const range = document.createRange();
        range.setStart(hello, 2);
        range.setEnd(world, 5);
        println(range.toString());
    });
</script>
Meta: Add DOCTYPEs to most text tests 2025-03-18 19:28:35 +01:00			`<!DOCTYPE html>`
LibWeb: Use UTF-16 code unit offsets in Range::to_string Similar to another problem we had in CharacterData, we were assuming that the offsets were raw utf8 byte offsets into the data, instead of utf16 code units. Fix this by using the substring helpers in CharacterData to get the text data from the Range. There are more instances of this issue around the place that we will need to track down and add tests for, but this fixes one of them :^) For the test included in this commit, we were previously returning: llo💨😮 Instead of the expected: llo💨😮 Wo 2024-01-04 10:27:25 +13:00			`<body><p id="p1"><b>Hello💨</b>😮 World</p>`
			`<script src="../include.js"></script>`
			`<script>`
			`test(() => {`
			`const p1 = document.getElementById("p1");`
			`const hello = p1.firstChild.firstChild;`
			`const world = p1.lastChild;`
			`const range = document.createRange();`
			`range.setStart(hello, 2);`
			`range.setEnd(world, 5);`
			`println(range.toString());`
			`});`
			`</script>`