Re: [selection-api] caret-based selection movement (#27)

Why would we not specify hat a sentence and what a paragraph are, if these are important for caret movement? Just because we define it, doesn't mean that all browsers are obliged to implement sentence/paragraph movement as a feature. It's just that once a specific browser decides to implement one of these features, they do so in a predictable manner.

The current situation, in which each browsers do a lot of things differently and even differ in their behavior from platform to platform and between browser versions is the main issue we are tying to deal with, as I understand it.

Currently many editors need to interrupt caret movements in Javascript and after a number of checks decide whether or not to let the default action go through. This is quite a lot of work just or right/left arrows. If additionally each browser does its own thing, which is unspec'ed (and likely not well documented), it becomes exponentially more difficult to get it right.

That being said, I agree that the normalization of the caret placement seems to be the most important thing here.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/27#issuecomment-66908765