Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)

Ok, I understand  that you want to understand why this is a problem. Let's for a moment forget about all the bugginess of contenteditable, and just think of a plain example in a browser that just works:

```

<div contenteditable=true>
<span class="digitalone"><span class="digitaltwo">Some words</span></span>
</div>

```

When writing at the end of  `digitalone` I want it to expand with the new text. When writing in `digitaltwo` I want new text at the end to fall outside of it. In practice, the only way to achieve this is by controlling the caret behaviro directly by JavaScript and doing various tricks. At anyr ate, I'm sure you'll easily find thousands of other such examples. Just look a little bit at the code of editors and you should easily find it. This is another of the top reasons why contenteditable needs to be replaced. 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing-explainer/issues/56#issuecomment-106154433