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

I also think that these details should be left to the browser. I also agree with having a "beforeselectionchange" event. The problem is what a webapp should do in response to this event.

I assume that the web app will call the Selection API to set a different selection if the browser proposed one is not desirable. However the current API for setting a selection changes only the visible part of the selection-associated state, i.e. the selected range, and clears the hidden selection-associated state, so we need a better Selection API. 

Maybe we can have some selection-changing API that also receives the intent of the selection change.


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