On Tue, Aug 14, 2012 at 4:16 PM, Glenn Adams <gl...@skynav.com> wrote:
> On Tue, Aug 14, 2012 at 3:36 PM, Ryosuke Niwa <rn...@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... > You can implement multi-range selection in WebKit and make all editing commands work, then please implement it by all means. - Ryosuke
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
