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

Re: [CSSOM] CaretPosition

From: Ojan Vafai <ojan@chromium.org>
Date: Fri, 6 May 2011 12:45:45 -0700
Message-ID: <BANLkTi=-JK-nDA7=4Q5=zCYB5C+fBUOmUQ@mail.gmail.com>
To: "Olli@pettay.fi" <Olli@pettay.fi>
Cc: "www-style@w3.org" <www-style@w3.org>
On Tue, May 3, 2011 at 2:18 AM, Olli Pettay <Olli.Pettay@helsinki.fi> wrote:

> On 05/03/2011 12:13 PM, Olli Pettay wrote:
>
>> Hi all,
>>
>> I wonder what is the use case for CaretPosition.range.
>> Is that mainly just a left-over from the old caretRangeFromPoint?
>> If the range is really needed, it would be trivial to
>> create one using CaretPosition.offsetNode and CaretPosition.offset.
>>
>> So, could we drop CaretPosition.range, before it gets implemented.
>>
>
> especially because
> http://dev.w3.org/csswg/cssom-view/#dom-document-caretpositionfrompoint is
> tiny bit inconsistent because of that
> range object. .range may or may not be null depending on which
> coordinates are used.
>

I agree. It would be great if the next iteration of DOM Ranges could spec
Ranges as having a startPosition/endPosition that were CaretPositions. This
is how WebKit's implementation works under the hood and it's much better
than dealing with node/offset pairs all the time.

Ojan
Received on Friday, 6 May 2011 19:46:30 GMT

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