On Sat, Jun 25, 2011 at 3:25 AM, Ryosuke Niwa <rniwa@webkit.org> wrote: > 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. > Can you explain further? Rob -- "If we claim to be without sin, we deceive ourselves and the truth is not in us. If we confess our sins, he is faithful and just and will forgive us our sins and purify us from all unrighteousness. If we claim we have not sinned, we make him out to be a liar and his word is not in us." [1 John 1:8-10]
Received on Saturday, 25 June 2011 10:24:36 UTC