W3C home > Mailing lists > Public > www-style@w3.org > June 2011

Re: [CSSOM] does CaretPosition need a "before/after" hint?

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Fri, 24 Jun 2011 08:25:42 -0700
Message-ID: <BANLkTi=OEBimbBc8Zes2MFOWk49StaffGw@mail.gmail.com>
To: robert@ocallahan.org
Cc: Ojan Vafai <ojan@chromium.org>, Anne van Kesteren <annevk@opera.com>, Julie Parent <jparent@chromium.org>, Eric Seidel <eseidel@chromium.org>, "www-style@w3.org" <www-style@w3.org>
On Fri, Jun 24, 2011 at 6:00 AM, Robert O'Callahan <robert@ocallahan.org>wrote:

> On Fri, Jun 24, 2011 at 7:46 AM, Ryosuke Niwa <rniwa@webkit.org> wrote:
>
>> Because they're two different things.  One is about whether a caret
>> appears before or after a line break, and the other is about to which
>> BiDi-level caret belongs.  Just because Gecko decides to reuse the same flag
>> doesn't mean we need to expose that to the Web.
>>
>> Having a flag that changes the meaning depending on where the
>> CaretPosition is seems like an unnecessary complexity.
>>
>
> The way I see it, the meaning doesn't change. When the caret is between two
> characters or elements in the DOM, you can think of it as being attached
> either to the previous character/element or the following character/element,
> and the flag tells you which case it is.
>
> So far, certain situations involving line-breaks and bidi are the only
> situations that we know of where it makes a difference to observable
> behavior.
>

On Mac, for example, the notion of caret being attached to before/after a
character doesn't really exist because it uses a split caret.

- Ryosuke
Received on Friday, 24 June 2011 15:26:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:41 GMT