- From: Ben Peters <Ben.Peters@microsoft.com>
- Date: Mon, 26 May 2014 23:47:23 +0000
- To: Robin Berjon <robin@w3.org>, Norbert Lindenberg <w3@lindenbergsoftware.com>
- CC: Jonas Sicking <jonas@sicking.cc>, Piotr Koszuliński <p.koszulinski@cksource.com>, public-webapps <public-webapps@w3.org>
> -----Original Message----- > From: Robin Berjon [mailto:robin@w3.org] > Sent: Monday, May 26, 2014 1:41 AM > To: Norbert Lindenberg > Cc: Jonas Sicking; Piotr Koszuliński; Ben Peters; public-webapps > Subject: Re: contentEditable=minimal > > On 26/05/2014 05:43 , Norbert Lindenberg wrote: > > On May 23, 2014, at 5:19 , Robin Berjon <robin@w3.org> wrote: > >> Which brings me to think: when we discussed this at the Summit, there > >> was some agreement (between all four of us :) that it was a good idea > >> to support multi-range selections. These are useful not just for > >> tables, but also for bidi. The reason for the latter is that when > >> selecting a line with multiple embedded directions (using a mouse), > >> you want to have the visual selection be an unbroken line (as opposed > >> to the crazy jumping around you get if you follow logical order). > > > > Were any speakers of bidirectional languages in the room when this was > > discussed? > > I don't know what languages the others speak. That said, my recollection was > that this was presented along the lines of "we've had regular requests to > support selecting text in geometric rather than logical orders". > > If that turns out not to be the case and we can stick to single-range selections, > it would certainly make the Selection API simpler. > I have also heard these requests from the bi-directional experts here at Microsoft. A single, unbroken selection is what we're told users want, and multi-selection makes this possible.
Received on Monday, 26 May 2014 23:47:54 UTC