29529 - Hitting return repeatedly in a <p> gives unexpected results

Status: VERIFIED FIXED

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

Description

[Simon Fraser [no longer active]]

To reproduce:
1. Load a file in composer that has a single <p> containing several lines of text 
inside the body.
2. Click in the text in the <p>
3. Hit Return a number of times. Here's what happens:

Before modification, source is
<p>
One of the suggestions that came out of this change was to do
notifications based on a timer rather than relying on network chunking.
The current set of changes enable that.
</p>

First Return (gives appearance of new line, as expected):

<p>
One of the suggestions that came out of this change was to do
n<br>
otifications based on a timer rather than relying on network chunking.
The current set of changes enable that.
</p>

Second Return (another new line, good!):

<p>
One of the suggestions that came out of this change was to do
n</p>
<p>otifications based on a timer rather than relying on network chunking.
The current set of changes enable that.
</p>

Third Return (yet another new line -- excellent!)

<p>
One of the suggestions that came out of this change was to do
n</p>
<p>

<br>

otifications based on a timer rather than relying on network chunking.
The current set of changes enable that.
</p>

Fourth return -- now things get screwey. We appear to _remove_ a blank line,
so the text under the space moves up:

<p>
One of the suggestions that came out of this change was to do
n</p>
<p>otifications based on a timer rather than relying on network chunking.
The current set of changes enable that.
</p>

Whoops! We've removed the <br>, but not replaced it with anything.

Comment 1

[Kathleen :Brade]

I think a lot of people will try to add several blank lines when editing e-mail 
or html files and may run into this so marking as "dogfood"

Comment 2

[leger]

Putting on PDT- radar for beta1.  Unless this can be labeled as "braindead 
trivial" (per rickg :-)  Then, remove PDT-, give us info and resubmit to PDT.

Comment 3

[Joe Francis]

m15

Comment 4

[Kathleen :Brade]

This bug is still present with Joe's changes in my Mac build.

Comment 5

[Joe Francis]

fixed (waot for tomorrows build)

Comment 6

[sujay]

verified in 7/27 build.