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

Because basically we cannot really trust the browser in move the caret where the app needs it to  anyway, so following @kojiishi's request:

> Are we not defining any default handlers for these intents? No default handles for arrow keys too?

> The original intention of this issue is that I just want the behavior clearly defined, so if the spec defines no default handlers, things should be easier.

I have just turned the caret movement into intentions that aren't handled by the browser. 

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