105668 - plaintext reply: delete quoted text, extra line inserted, cannot move caret to top of textarea

Status: VERIFIED WORKSFORME

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

Description

[Leston Buell]

This may be related to bug 93536. Follow these steps:

1. Start a quoted plaintext reply to a message. 
2. Delete a few lines from the very beginning of the quoted text.

Expected result:
   One blank line at the top of the textarea, with the cursor on that line.

Actual result:
   Two blank lines at the top of the textarea. The cursor is on the second 
   blank line. The cursor cannot be moved to the first blank line, which 
   is at the top of the textarea.

Reproducible always. I'm using Linux 2001-10-18-08-trunk, but this has been
around for some time.

Comment 1

[Jean-Francois Ducarroz]

reassign to editor

Comment 2

[sujay]

Kin, who does this go to ?

Comment 3

[kinmoz]

This sounds like an editor core problem. Taking.

Comment 4

[Christopher Aillon (sabbatical, not receiving bugmail)]

Marking new.

Comment 5

[Syd Logan]

plussing

Comment 6

[Hixie (not reading bugmail)]

I can no longer reproduce this bug.

Reporter: Are you still seeing this?

Comment 7

[kinmoz]

I'm having a hard time reproducing this problem in my 01/24/02 debug build. Of
course 93536 was fixed so, I'm not sure if this was related or not. jfrancis?

Just be sure of some things ... you were using a Plaintext Mail Compose window
(no html toolbar), and when you reply, each line of the reply text is preceded
by a '>' character, not a blue bar, right? Also, what is your reply starts at
top/bottom pref set to?

Comment 8

[kinmoz]

I still can't reproduce this. Leston if you are still seeing this bug with a
recent TRUNK build, or the mozilla0.9.8 milestone build, please reopen. Also if
you could answer some of the questions above it might help us reproduce the
problem if it's still there.

Comment 9

[Leston Buell]

(I'm the reporter.) Sorry for not being attentive to those questions. I don't
seem to reproduce this anymore myself. I don't recall experiencing this bug for
quite a while. So, WORKSFORME is appropriate.

Comment 10

[sujay]

verified.