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

Right, we can spec that non-editable elements are treated like a single character.

The problem with word boundary movements is that the treatment of whitespace is different amongst browsers. e.g. trailing or leading whitespace may or may not be considered as a part of a word.  Also, in Chinese and Japanese, word boundaries can only be determined by heuristics.  See http://www.quora.com/What-are-some-Japanese-tokenizers-or-tokenization-strategies

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