Open
Bug 886252
Opened 12 years ago
Updated 3 years ago
deleting 'wrote:' line in html reply to (mime) plain text email joins all lines
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: davidmaxwaterman, Unassigned)
Details
Attachments
(1 file)
719 bytes,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release)
Build ID: 20130512193848
Steps to reproduce:
tb: 17.0.6 ubuntu: 13.04
1) reply to a plain text email like the one attached using the html compose mode
compose shows something like :
On sometime, someone wrote:
| message
| message
| and so one
The 'wrote:' line is in 'Body Text', but the quoted text is 'Preformat'.
2) select all (ctrl-a)
all text is selected
3) click 'outdent' icon
all quoted text is outdented so that '|' are removed - formatting is maintained ie the previously quoted text is 'preformat' and 'wrote:' line is 'Body Text'.
4) position cursor at end of 'wrote:' line, ie after the colon
5) hit 'delete'
Actual results:
all (previously) quoted text is joined into a single line following the ':', and formatting is changed from 'Preformat' to 'Body Text'.
Expected results:
the first line of the quoted text should be moved up to the end of the 'wrote:' line. It isn't so important if the moved text is converted into 'Body Text' or remains as 'Preformat'.
When I attempt to reproduce myself with Thunderbird, I can't get it to fail - I suspect the difference in MIME headers.
Broken (probably sent by Microsoft Outlook) :
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Working (Thunderbird):
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Let me know if I have removed too much from the headers on the attached file.
Reporter | ||
Comment 1•12 years ago
|
||
I notice a similar effect if you select the whole message and change it from "Mixed" to "Body Text" - perhaps this bug is the same thing (and I think I recall seeing another bug with this sort of desciption).
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•