W3C home > Mailing lists > Public > www-style@w3.org > February 2010

[CSSOM] getClientRects should work on collapsed ranges in elements

From: Ojan Vafai <ojan@chromium.org>
Date: Wed, 10 Feb 2010 16:48:46 -0800
Message-ID: <78dc8441002101648j5aa411e8n4780d68de2218286@mail.gmail.com>
To: www-style@w3.org, Daniel Danilatos <danilatos@google.com>, Julie Parent <jparent@chromium.org>, Tony Chang <tony@chromium.org>, "TAMURA, Kent" <tkent@chromium.org>, Roland Steiner <rolandsteiner@google.com>
Given the following DOM and default CSS styling:

I think it makes sense that getClientRects would return the same result for
the following ranges as they all correspond to the same visible position
(e.g. when a text input caret is there):
1. startNode: div, startOffset: 0
2. startNode: span, startOffset: 0
3. startNode: textnode, startOffset: 0

With the current spec 1 and 2 return the empty list and 3 returns a
zero-width rect. They should all return a zero-width rect with the same
values, which matches IE (in the cases where IE TextRanges can represent the
same Range).

The only use-case I can think of for getClientRects is to get the position
of the Selection for putting up context-specific menus. This makes the API
hard to use if code needs to first ensure that the endpoints are in
textnodes (e.g. in the empty span case, the code would need to first insert
a text node).

An alternative is to add getClientRects to the Selection object. That seems
a bit redundant to adding it to Ranges, but more importantly means that
calling code would need to modify the actual selection in order to get this

Received on Thursday, 11 February 2010 00:49:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:42 UTC