This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29562 - Define Range.getClientRects() when the range contains part of a grapheme cluster, a surrogate pair, or a ligature
Summary: Define Range.getClientRects() when the range contains part of a grapheme clus...
Status: RESOLVED FIXED
Alias: None
Product: CSS
Classification: Unclassified
Component: CSSOM View (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Simon Pieters
QA Contact: public-css-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-07 11:35 UTC by Koji Ishii
Modified: 2016-04-14 13:18 UTC (History)
0 users

See Also:

Attachments

Description Koji Ishii 2016-04-07 11:35:17 UTC 
We recently figured out that the spec[1] isn't clear when the range
contains part of a grapheme cluster. Our behavior for the case was recently
changed due to some other improvements, which lead to a discussion of the
right behavior of getClientRects() and getBoundingClientRect().

Could we define cases such as:
1. What to do when the range contains part of a grapheme cluster.
2. What to do when the range contains part of a surrogate pair.
3. What to do when the range contains part of a ligature.

[1] http://drafts.csswg.org/cssom-view/#extensions-to-the-range-interface

The thread at www-style:
https://lists.w3.org/Archives/Public/www-style/2016Apr/0115.html

View the thread in readable-email:
https://readable-email.org/list/www-style/topic/cssom-view-range-getclientrects-when-the-range-contains-part-of-a-grapheme-cluster