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

That there are differences between browsers or operating systems doesn't necessarily preclude a spec. For space handling, we could specify two alternatives, and say that a browser can choose which one to use, but that it has to stick with it at least for the lifetime of the document, and that it cannot invent something different. For word boundaries, we can say that the determination of the word itself is implementation dependent, but then specify the behavior relying on the word boundaries.

You can see this in the specification for NumberFormat.prototype.format in the ECMAScript Internationalization API: The spec is very precise as to how to map a number to a string of digits, but then leaves several aspects of the localization of this string implementation dependent, such as which digits to use for which locale, or which decimal and grouping separators to use or where to insert the grouping separators. The idea is that the numeric value should be recognizable in any localized format.
http://www.ecma-international.org/ecma-402/1.0/#sec-11.3.2

The question though is what level if precision would help application developers.

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