Re: [w3c/selection-api] Specify Selection.modify()? (#37)

Well, the problem here is that there appears to be a fundamental disagreement about what these APIs are for. Gecko, for example, has one behavior for how a whiteface around a word is treated in languages in which a word boundary is defined by white spaces across all platforms for `modify()` even though selection will be moved and extended differently on Mac & Windows by the user. WebKit (and Blink) for most part respected each platform's convention with regards to the treatments of whitespace even in `modify`.

Furthermore, moving caret or extending selection across word boundary is a fundamentally non-interoperable feature because the definition of a word boundary is not set in stone in many languages. For example, in Chinese and Japanese, there are no syntactical hint or mechanism to define a word boundary. As such, ICU relies on a bunch of heuristics and dictionary lookups to determine where the word boundary might be. This in turn means that each browser & platform has a different definition of what a word boundary means.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/37#issuecomment-285618049