The first manifestation of this problem appeared during a cut/paste operation. I think it might relate to the start of the composotion buffer... but I haven't figured it out. Secondary manifestations have similar (strange permutation) effects. I think I've seen bugs like this years ago... and I think cmanske worked on it... so I'm copying him. a) create a few lines of text in a mail compose window b) go to another app (4.7?) and cut a 4 line paragraph from the start of another message c) Try to paste the paragraph at the *start* of the seamonkey composition window Notice that rather than seeing the lines 1,2,3,4, they appear as 2,3,4,1 (i.e., the first line was made last). d) Past another copy of the paragraph. Notice that now you have two copies, with the lines appearing as 2,3,4,1 and 2,3,4,1. e) Delete the first three lines of the buffer Now you have 1 followed by 2,3,4,1 f) Delete the trailing (5th) line which was a dup of the first line Now you have 1 followed by 2,3,4 g) Try to delete the CR at the end of each line to get the lines to flow together. First delete the CR at the end of line 3 (getting 4 to flow in). Then delete the CR at the end of line 2 (to get 3 to flow in). Finally, delete the CR at the end of line 1. Incredibly, line 1 now jumps to the end of the paragraph!!

qa contact to sujay

assigning to jfrancis

Putting on PDT+ radar.

investigating...

I cant reproduce this on an outofdate build. Making a new build. I'll go bug someone else with a fresh build and see if it shows up.

I can't reprocude this on todays build, or old builds. I need to know some more details. Was this an html paste or a raw text paste? Also, was there any inline style involved? Finally, when you pasted and saw the lines in the worng order, what were there results of "Output HTML" (Debug Menu) and also "Dump Content Tree" (also Debug Menu).

I can't seem to reproduce this bug either. I'm using the 12/15/1999 SeaMonkey install.

mjudge, akkana, and sfraser also all tried and failed to reproduce this bug. Jar? Can you give us a hand here?

I just tried to reproduce this a few times... and it appears fixed... so you can mark it either worksforme, or fixed, depending on whether you've been doing stuff that impacts the start of the composition buffer or not. Thanks, Jim

I'll just mark it worksforme --Jar, if it happens again, then please open a new bug -- thanks

verified in 12/16 build.

*** Bug 24642 has been marked as a duplicate of this bug. ***