> > This appears to make visual selection appealing--although it doesn't, for
> > the
> reasons mentioned elsewhere, lead to sensible text operations unless the
> selected run happens to be all in a single direction.
>
> and if the text runs all in a single direction, there's no difference betwee
On 15/08/2015 22:24, Phillips, Addison wrote:
This appears to make visual selection appealing--although it doesn't, for the
reasons mentioned elsewhere, lead to sensible text operations unless the
selected run happens to be all in a single direction.
and if the text runs all in a single direc
On Sat, Aug 15, 2015 at 9:04 PM, Richard Ishida wrote:
> my question was specifically, why do it in a non-standard way for bidi text?
> (typical scenario is split visual but one range internally)
Which is not great for users, right? Also, as Addison points out, it's
unclear how that would work on
> >> what's the use case driving this, and where are the requirements
> >> coming from?
> >>
> >> i ask because i'm inclined to think that the circumstances in which
> >> this would a produce useful results, given the way it carves up the
> >> actual content, are quite, perhaps extremely, limited.
..@annevk.nl]
Sent: Saturday, August 15, 2015 8:20 AM
To: Ryosuke Niwaa
Cc: public-webapps; Ehsan Akhgari; Aryeh Gregor; public-editing-tf;
www-internatio...@w3.org
Subject: Re: Copying multi-range selection
On Sat, Aug 15, 2015 at 12:10 AM, Ryosuke Niwa wrote:
> We've been recently exp
On 15/08/2015 13:38, Anne van Kesteren wrote:
On Sat, Aug 15, 2015 at 10:23 AM, Richard Ishida wrote:
what's the use case driving this, and where are the requirements coming
from?
i ask because i'm inclined to think that the circumstances in which this
would a produce useful results, given the
On Sat, Aug 15, 2015 at 8:38 AM, Anne van Kesteren wrote:
> On Sat, Aug 15, 2015 at 10:23 AM, Richard Ishida wrote:
> > what's the use case driving this, and where are the requirements coming
> > from?
> >
> > i ask because i'm inclined to think that the circumstances in which this
> > would a p
On Sat, Aug 15, 2015 at 10:23 AM, Richard Ishida wrote:
> what's the use case driving this, and where are the requirements coming
> from?
>
> i ask because i'm inclined to think that the circumstances in which this
> would a produce useful results, given the way it carves up the actual
> content,
Hi Anne,
Not sure if this would answer your question, but in general, when it comes to
BiDi you need to differentiate between the physical order (what is in memory,
e.g, ABC) and the logical order (what the user expects to see (e.g., CBA). At
the same time to handle copy/paste, you will be con
On 15/08/2015 06:19, Anne van Kesteren wrote:
On Sat, Aug 15, 2015 at 12:10 AM, Ryosuke Niwa wrote:
We've been recently exploring ways to select bidirectional text and content
that uses new CSS layout modes such as flex box in visually contagious manner.
Because visually contagious range of c
We worked on this some years ago, and found that the cut/copy/paste were
very, very complicated to get to be natural, and ended up dropping it.
The problem is that if ...ABC... are adjacent ranges on the screen in the
source (each letter is a range), people expect to see ...ABC... when it is
paste
On Sat, Aug 15, 2015 at 12:10 AM, Ryosuke Niwa wrote:
> We've been recently exploring ways to select bidirectional text and content
> that uses new CSS layout modes such as flex box in visually contagious manner.
>
> Because visually contagious range of content may not be contagious in DOM
> ord
12 matches
Mail list logo
