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

> @Reinmar: As for 3: Notice that we renamed the spec after removing any kind of caret movement or input behavior. This is still interesting of course and will have to be added eventually, but it is my understanding that this has been moved to a future "cE=caret" spec.

Frankly speaking, I do not understand this move (stripping even caret movements), but I'll perhaps post a separate question about that. (Were there any discussions that would explain this decision?)

> In the meantime we need to be sure that the primitives are in place so that caret movement can be fully handled through JavaScript.

So perhaps the primitives are exactly as I described – selection methods simulating intentions of arrow keys? As they are supposed to replace the native default actions the most convenient for us, developers, would be if usage of them didn't require any additional tinkering. In 99% cases a developer using `cE=events` will try to recreate the native behaviour (that's also why I'm not sure if stripping this makes sense).

BTW. What about making a selection on touch screen devices and using mouse? So far the discussion was about caret movements and I can see that the input events explainer also describes only caret-related events. Have other cases been discussed already? 

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