14140 2011-09-13 13:29:27 +0000 Use CaretPosition for range boundary points? 2012-05-15 10:49:13 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED WONTFIX P2 normal --- 1 annevk annevk ayg mike www-dom public-webapps-bugzilla oldest_to_newest 56746 0 annevk 2011-09-13 13:29:27 +0000 Should range boundary points have an object representation in the form of http://www.w3.org/TR/cssom-view/#caretposition and should that interface therefore carry a slightly different name? 56760 1 ayg 2011-09-13 20:38:27 +0000 The semantics of CaretPosition are slightly but significantly different. For <input> or <textarea> or such, the offset of a CaretPosition (at least as returned by caretPositionFromPoint()) is the offset into the element's value, not its children. An object representation of a boundary point would have been great to have, because maybe it would have averted insanity like the first argument of Range.compareBoundaryPoints. But I think it's too late now to usefully add such an interface. What would we do with it? There's too much redundancy in Range as it stands. 67719 2 annevk 2012-05-15 10:49:13 +0000 Nobody seems to care much for this.