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

@rniwa: Given that we already can find the current caret position (using something like document.getSelection().getRangeAt(0).getClientRects()[0] ), I wonder if an `beforeselectionchange` event would give us all the information we need to have to implement the two versions of arrow up/down that have been mentioned. Especially given that it seems Safari is not willing to expose more simple underlying pieces of data for now. The `beforeselectionchange` event would give us a range corresponding to where the caret would be after the update, unless preventDefault is called on that event, right? 

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