Open GoogleCodeExporter opened 9 years ago
found the same problem in Internet Explorer 6 / Windows XP SP3
Original comment by leei...@gmail.com
on 12 Jul 2009 at 1:03
The fix for this requires some special handling of the case where the offset is
beyond the end of the child nodes within the container. My company (Pearl
Crescent) has applied several fixes to convertFromDOMRange, including one for
this issue. I will attach the code we are using.
Original comment by markcsm...@gmail.com
on 8 Mar 2011 at 4:40
Attachments:
We had a contenteditable field with some <em>'s inside.
This fix
line 82
- cursor.compareEndPoints(bStart ? 'StartToStart' : 'StartToEnd',
textRange) > 0
+ cursor.compareEndPoints(bStart ? 'StartToStart' : 'StartToEnd',
textRange) >= 0
and that
line 85
- if (cursor.compareEndPoints(bStart ? 'StartToStart' : 'StartToEnd',
textRange) == -1 && cursorNode.nextSibling) {
+ if (cursor.compareEndPoints(bStart ? 'StartToStart' : 'StartToEnd',
textRange) <= 0 && cursorNode.nextSibling) {
helped us much.
Win 7, IE 9.
Original comment by daftcode...@gmail.com
on 16 Jul 2012 at 1:23
Original issue reported on code.google.com by
TakiTake...@gmail.com
on 2 Jun 2009 at 9:15