Closed Bug 493111 Opened 14 years ago Closed 13 years ago
"ASSERTION: Range index not returned"
editor/libeditor/html/crashtests/336081-1.xhtml triggers ###!!! ASSERTION: Range index not returned: 'rangeIndex >= 0', file /Users/jruderman/central/layout/generic/nsSelection.cpp, line 4990
More fallout from bug 348681. The "overlap" case in AddItem fails to correctly set aOutIndex, triggering the assertion.
Assignee: nobody → graememcc_firefox
Status: NEW → ASSIGNED
Attachment #401669 - Flags: review?(roc)
Attachment #401669 - Flags: review?(roc) → review+
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a1
Attachment #401669 - Flags: approval1.9.2?
Comment on attachment 401669 [details] [diff] [review] Patch v1 Requesting a1.9.2 for a trivial fix: aside from the assertion spew in debug builds, in certain circumstances this could cause unpredictable behaviour when performing multiple selections, as failing to return the index of the new range would lead to the focus and anchor nodes being reported as null.
Comment on attachment 401669 [details] [diff] [review] Patch v1 a1.9.2=dbaron But you should add showfunc = 1 to the [diff] section of your ~/.hgrc .
Attachment #401669 - Flags: approval1.9.2? → approval1.9.2+
You need to log in before you can comment on or make changes to this bug.