[Webkit-unassigned] [Bug 23601] DOMSelection.getRangeAt() returns a different range than the selection

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 5 14:30:42 PST 2009


------- Comment #7 from ap at webkit.org  2009-02-05 14:30 PDT -------
(In reply to comment #4)
> Why oh why would toRange chose to modify the Selection instead of just
> returning the range?

I think the reason is that Selection positions may be invalid in DOM sense, so
calling rangeCompliantEquivalent() is necessary. As Justin says, the validate()
call during selection creation is the real culprit.

See also: bug 15256 and the many related ones.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list