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

> I completely agree that one of the biggest "missing pieces" for editor devs is the complete lack of visibility into how a text node is laid out. To know where a line-wrap occurs we have to do some ridiculous hacky and error-prone gymnastics.

@teleclimber Are you aware of the  `Box Tree API` specification the `CSS Houdini` group is working on? http://dev.w3.org/houdini/box-tree-api/ . This will (hopefully) come, but it's somewhat further in the future, most likely.

I think that if for now we could simply get a function to "Where would caret go, if it should be close as possible to position X" or so, then we should be able to do most types of caret up/down movements ourselves.

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