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

@Reinmar Do I guess correctly that then none of us quite know if it is possible to do block direction caret movement on all browsers/platforms using only JS without problems? I meantion those two projects, because:

* The ProseMirror developer is also behind CodeMirror, in which contenteditable is not used. The CodeMirror editor has also been adopted for richtext editing by some projects, yet for some reason he chose to use contenteditable on ProseMirror, and he mentions caret movement. He has responded earlier with some ideas about requirements, but we haven't heard as much from them as from you guys from CKEditor.

* The Aloha 2 people have at least tried to do block direction caret movement entirely in JS (without splitting lines manually), yet I don't think we have heard much from them since the Extensible Web Summit last fall in Berlin. So we don't know if they ran into fundamental issues with caret movement or whether they are dealing with many other bugs. From Github I can tell they have mainly been working on their Aloha 1 editor (the one that is built on contenteditable) for the last few months.

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