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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 6 10:27:08 PST 2009


------- Comment #15 from eric at webkit.org  2009-02-06 10:27 PDT -------
Ap also reviewed and suggested that I add rangeCompliantEquivalent calls to
firstRange().  I'm not sure that adding rangeCompliantEquivalent is correct in
all cases (it seems to avoid having positions in tables!?) but it will fix any
invalid (img, 1) positions (which I don't know how to generate), which sounds
like a good thing.

I'm going to leave it as toNormalizedRange() because I feel it better implies
that the function does work. :)  firstRange doesn't really need to do work, if
we stored start/end as a Range.  I'd like to discourage people from calling
toNormalizedRange,cause I don't think it's what most callers actually
need/want.  I think the logic is misplaced.

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