HTML reply to plain text message with quoting contains spurious comment

RESOLVED WONTFIX

Status

MailNews Core
Composition
--
minor
RESOLVED WONTFIX
17 years ago
9 years ago

People

(Reporter: neil@parkwaycc.co.uk, Assigned: Jean-Francois Ducarroz)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
Using Build ID: 2001060704

Steps to reproduce problem:
1. Find a plain text message with quoted text.
2. Create a Reply to that message in HTML format.
3. Copy the message body.
4. Open a new editor window.
5. Paste the message in.
6. Switch to HTML source.

Actual results: <pre><!----><br> in source.

Expected results: No empty comment in source.
(Assignee)

Updated

16 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Blocks: 152942

Comment 1

16 years ago
I inserted that HTML comment specifically to prevent unforable layout (I think
in Gecko, don't remember). There's a C++ comment in the C++ source code.

WONTFIX.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
OS: Windows 95 → All
Hardware: PC → All
Resolution: --- → WONTFIX

Comment 2

16 years ago
s/unforable/unfavorable (bad)/
(Reporter)

Comment 3

16 years ago
Just out of interest, where in the source code? I can't search for <!---->

Comment 4

16 years ago
mimetpla.cpp, I think.

Comment 5

16 years ago
<http://lxr.mozilla.org/seamonkey/source/mailnews/mime/src/mimetpla.cpp#387>

386       if (text->mCiteLevel == 0)
387         prefaceResultStr += "<!---->";   /* Make sure, NGLayout puts out
388                                             a linebreak */
(Reporter)

Comment 6

16 years ago
I'm afraid I don't understand why it's only needed inside the outermost quote or
in fact at all (I used Select All/Insert HTML to add and remove it and couldn't
detect any difference). Perhaps it's to work around a subsequently fixed bug :-)

Comment 7

16 years ago
I didn't understand it either. It was just the way it was back then. Looked like
a bug, but not sure. Yes, maybe it's fixed in the meantime, but maybe we want to
preserve backwards compatibility with those older Mozillas, unless they are very
old. I certainly don't care enough to investigate all that.

Comment 8

15 years ago
->esther
QA Contact: sheelar → esther
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.