ladybird/Tests/LibWeb/Text/input/Editing/move-cursor-using-selection-api.html

<!DOCTYPE html>
<script src="../include.js"></script>
<div id="text" contenteditable="true">heo</div>
<script>
    test(() => {
        let text = document.getElementById("text");
        text.focus();
        document.getSelection().collapse(text.firstChild, 2);
        internals.sendText(text, "lll");
        println(text.textContent);
    });
</script>
Meta: Add DOCTYPEs to most text tests 2025-03-18 15:28:35 -03:00			`<!DOCTYPE html>`
LibWeb: Separate text control input events handling from contenteditable This input event handling change is intended to address the following design issues: - Having `DOM::Position` is unnecessary complexity when `Selection` exists because caret position could be described by the selection object with a collapsed state. Before this change, we had to synchronize those whenever one of them was modified, and there were already bugs caused by that, i.e., caret position was not changed when selection offset was modified from the JS side. - Selection API exposes selection offset within `<textarea>` and `<input>`, which is not supposed to happen. These objects should manage their selection state by themselves and have selection offset even when they are not displayed. - `EventHandler` looks only at `DOM::Text` owned by `DOM::Position` while doing text manipulations. It works fine for `<input>` and `<textarea>`, but `contenteditable` needs to consider all text descendant text nodes; i.e., if the cursor is moved outside of `DOM::Text`, we need to look for an adjacent text node to move the cursor there. With this change, `EventHandler` no longer does direct manipulations on caret position or text content, but instead delegates them to the active `InputEventsTarget`, which could be either `FormAssociatedTextControlElement` (for `<input>` and `<textarea>`) or `EditingHostManager` (for `contenteditable`). The `Selection` object is used to manage both selection and caret position for `contenteditable`, and text control elements manage their own selection state that is not exposed by Selection API. This change improves text editing on Discord, as now we don't have to refocus the `contenteditable` element after character input. The problem was that selection manipulations from the JS side were not propagated to `DOM::Position`. I expect this change to make future correctness improvements for `contenteditable` (and `designMode`) easier, as now it's decoupled from `<input>` and `<textarea>` and separated from `EventHandler`, which is quite a busy file. 2024-10-23 16:26:58 -03:00			`<script src="../include.js"></script>`
			`<div id="text" contenteditable="true">heo</div>`
			`<script>`
			`test(() => {`
			`let text = document.getElementById("text");`
			`text.focus();`
			`document.getSelection().collapse(text.firstChild, 2);`
			`internals.sendText(text, "lll");`
			`println(text.textContent);`
			`});`
			`</script>`