Re: [editing] ContentEditable with UserSelect=None needs to be documented (#20)

@kojiishi: It may be a misunderstanding, but one of your comments triggered me to remove all caret movement and turn them into intentions. the idea was just that nothing happens by default -- the caret is just placed in the first legal caret position within the cE=Typing element and everything beyond that will happen via JS.

The only other thing that probably needed go into contentEdtiable=Typing could be something about how a tab/mouse click is handled (an intention event or maybe use existing events).

Everything that is not about moving the caret using arrow keys, but rather general questions about how selections should work, should be defined in the selection API, I think.

Then later you made some other comments that made me think that you want caret movement back in to elements set as contentEditable=Typing. That's what ticket https://github.com/w3c/editing/issues/58 was opened for.


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