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

Ok, but this difference in how browsers behave is exactly what we want to stop by spec'ing things, right? The idea is to get behavior which editor developers (and end users) can rely on. If the caret moves an extra space in certain browsers while not in others, that can be the cause of a major headache for editor developers, who may find it easier to just override the word boundary movement mechanism altogether in order to ensure consistent behavior.

As for Japanese, Chinese, etc.: Could we spec word boundary movements for all text using the Roman or Greek alphabets?

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