[webkit-dev] Disjointed selection ranges

Glenn Adams glenn at skynav.com
Tue Aug 14 16:16:37 PDT 2012

On Tue, Aug 14, 2012 at 3:36 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:

> I have to admit there are some valid use cases for supporting multi-range
> selection but the complexity it adds to our codebase is unjustifiable.
> Gecko has tried this for a decade but they're now trying to get rid of it.
> See https://bugzilla.mozilla.org/show_bug.cgi?id=753718.

One could make the same (complexity) argument (and many have) against
supporting "complex" scripts in the first place. That is a pretty
subjective argument, when certain minorities have no choice but dealing
with things that many of us would find "complex" [look how long it took to
support Tibetan|Dzongkha]. For example, one might argue that Japanese
should start writing in romaji because kanji|kana is too complex. But that
argument never works.

Personally, I have implemented and supported disjoint, multi-range
selections in a number of high-end editing products (for the preprint
industry). I found this quite implementable, though admittedly not
straightforward. Anyway, that's my 2 cents worth on this thread...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120814/74886fac/attachment.html>

More information about the webkit-dev mailing list