Open Bug 125500 Opened 23 years ago Updated 4 years ago

When changing a selected list entry, erroneous source is created by Editor

Categories

(Core :: DOM: Editor, defect, P5)

x86
All
defect

Tracking

()

mozilla1.4beta

People

(Reporter: hwaara, Unassigned)

Details

1. Type some lines into Editor, and click the button to make them become and ordered list ("1", "2" etc.). 2. Select some of the items, right-click and choose "List Properties..." 3. Change only the selected items to be bullets instead of ordered items, click OK. 4. Now select one of the remaining ordered items, bring up "List Properties..." and choose to have the whole list be solid squares. Result: The list has now been split up into two lists. So when you try to change the whole list's properties, it will only change one of the lists.
--> jfrancis
Assignee: kin → jfrancis
Here's an even better testcase: 1. Create a new document 2. Put this source in between the body tags (remove the initial <br> in the new doc): <ol> <li>Hey</li> <li>Now</li> <ol> 3. Select "Hey", choose "Change only selected items" and make it be a bullet. The result is some pretty messed up and mangled source! Just check this output out: <ol> <li>Hey</li> </ol> <ul> <li>Now</li> </ul> <ol> <ol> </ol> </ol>
I'm not sure what calls Charlie is making here - I'll have to check. At any rate list properties bugs are probably safely deflected to 1.1
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
I was commenting on this once before! guess something went wrong. Anyway, I don't think there's any problem here except if we are generating the empty <ol> </ol> at the end of the "old" (numbered) list. Otherwise, changing one item from ordered to bulleted item *must* create new <ul> tags, i.e. "a new list"!
I do agree with Charlie that the only thing I see wrong is the trailing empty < ol>
The trailing <ol> list and the weird inserted newlines are both wrong, IMHO.
Summary: List gets split up → When changing a selected list entry, erroneous source is created by Editor
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.1alpha → mozilla1.2beta
[ushing these out as far as bugzilla will let me. I'll pull them back as I work on them.
Target Milestone: mozilla1.2beta → mozilla1.4beta
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: ASSIGNED → NEW

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: major → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.