I have an account set to compose messages in plain text (i.e., the "Compose messages in HTML format" box is unchecked). When I reply to a message, the message compose window appears; the line "On <timestamp>, <author> wrote:" appears followed by the quoted message. If I select this line and one or more subsequent lines and copy them to the clipboard, the first newline does not get copied. So when I paste the clipboard, the first line of the quoted message appears immediately after the colon. Reproducibility: Always Steps to reproduce: 1. Send yourself the following message: this is a test foo bar 2. Reply to the message. A composer window opens with the following: On 03/06/13 12:19 PM, Tristan Miller wrote: > this is a test > foo bar 3. Select and copy (or cut) the two lines to any clipboard. (This could be done by simply dragging the mouse, or by dragging the mouse and pressing Ctrl+C or Ctrl+Ins or Ctrl+X or Shift+Del, or by using the shift+arrow keys on the keyboard followed by Ctrl+C or Ctrl+Ins or Ctrl+X or Shift+Del.) 4. Paste the contents of the clipboard into the composer window or any other text editor. (This can be done by middle-clicking, or by Ctrl+V or Shift+Ins, depending on how the text was copied.) Expected behaviour: 5. The following text should appear at the cursor: On 03/06/13 12:19 PM, Tristan Miller wrote: > this is a test > foo bar Observed behaviour: 5. The following text appears at the cursor: On 03/06/13 12:19 PM, Tristan Miller wrote:> this is a test > foo bar
There's an error in my description of how to reproduce the problem. Specifically, in Step 3, the text "two lines" should actually be "three lines".
Can confirm this on Win32 (XP) and Thunderbird 24.2.0 Basically, the first new line character is thrown away, so it's enough to just copy&paste those two lines with the line break in them to see the bug. The bug only affects the transition between the reply header line ("On dd/mm/yyyy ..") and the first quoted line, e.g. the following newline characters are handled correctly.
No longer reproducible for me with Thunderbird 52.6.0. Should we close this or are others still affected?
You need to log in before you can comment on or make changes to this bug.