Assertion in range code when deleting last list items

NEW
Unassigned

Status

()

Core
Editor
P3
normal
17 years ago
11 years ago

People

(Reporter: Simon Fraser, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [behavior])

(Reporter)

Description

17 years ago
I see the following assertion in range code:

###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 
667

if I:
1. Load the attachment in composer
2. Select over all the list items
3. Delete them, leaving a single empty (hollow circle) list item
4. Hit delete again to remove the remaining list item.

Starting source:
<ul>
<li>
<div class="moz-text-html" style="font-family: Times; font-size: 12px; ">
<ul>
<li>Fixed bug 1234</li>
<li>Did some more work</li>
<li>Did other work</li>
</ul>
</div>
</li>
</ul>

Source after step 3:

<ul>
<li>
<div class="moz-text-html" style="font-family: Times; font-size: 12px; ">
<ul>
<li><br>
</li>
</ul>
</div>
</li>
</ul>

[note, when at this stage, and I go to HTML source and back, going back causes 
the following assertion:
###!!! ASSERTION: nsRange::PopRanges() got error from SetEnd(): 
'NS_SUCCEEDED(res)', file nsRange.cpp, line 890
]

HTML source after getting the assertion:

<ul>
<li>
<div class="moz-text-html" style="font-family: Times; font-size: 12px; ">
<ul>
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
</ul>
</div>
</li>
</ul>

Wow, where did those nbsp's come from?

Comment 1

17 years ago
moving to future until we can sort through fix dates
Target Milestone: --- → Future

Comment 2

17 years ago
moz 0.9
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9

Comment 3

17 years ago
moving a bunch of 0.9 bugs to 0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1

Updated

17 years ago
Target Milestone: mozilla0.9.1 → mozilla0.9.2

Comment 4

17 years ago
moving to 1.0
Keywords: correctness
Whiteboard: [behavior]
Target Milestone: mozilla0.9.2 → mozilla1.0

Comment 5

16 years ago
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1

Comment 6

16 years ago
The trunk is the wave of the future!
Target Milestone: mozilla1.0.1 → mozilla1.1beta

Comment 7

16 years ago
The days of having a half dozen milestones out in front of us to divide bugs 
between seem to be gone, though I dont know why.  Lumping everything together as 
far out as I can.  I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.1beta → mozilla1.2beta

Comment 8

16 years ago
similar report from charlie:
11:27 AM:    cmanske: jfrancis_: Do this: start numbered list, type 3 lines,
select all lines, change type via format menu to "Definition" ...
11:26 AM:    cmanske: asserts at:
11:27 AM:    cmanske: nsVoidArray::ElementAt(int 1) line 78 + 35 bytes
11:27 AM:    cmanske: nsRange::IsIncreasing(nsIDOMNode *
11:27 AM:    cmanske: nsRange::CompareBoundaryPoints(nsR
11:27 AM:    cmanske: nsHTMLEditRules::UpdateDocChangeRang

Comment 9

16 years ago
This is really annoying!
Keywords: nsbeta1
Hardware: Macintosh → All

Updated

16 years ago
Blocks: 162874

Updated

15 years ago
Target Milestone: mozilla1.2beta → M1

Comment 10

15 years ago
differentiating bug severity of my most critical bugs vai abuse of milestone field
M2: severe
M1: very severe and/or fix in hand
Target Milestone: M1 → M2
nsbeta1-
Keywords: nsbeta1 → nsbeta1-
happens on all operating systems
OS: Mac System 8.5 → All
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.