Closed Bug 58527 Opened 24 years ago Closed 5 years ago

Recognition ran for SaveAsDraft of HTML msg

Categories

(MailNews Core :: MIME, defect)

Product:
MailNews Core
Component:
MIME
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
Future

People

(Reporter: BenB, Unassigned)

Details

Reproduce:
1. Open HTML composer
2. Type "ftp.mozilla.org" into body
3. Save as draft
4. Close composer
5. Open draft (-> HTML composer comes up again)
6. Send

Actual result:
"ftp.mozilla.org <ftp.mozilla.org>" is sent.

Expected result:
"ftp.mozilla.org" is sent.

Additional Comments:
I don't know what exactly is going on, but I guess, we run the recognition
during SaveAsDraft. Will have to investigate more.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
reassigning to ducarroz
Assignee: rhp → ducarroz
Status: ASSIGNED → NEW
This bug messes up my mails. I don't want to excuse for my buggy mailer.
mozilla0.9.2 and (being a bit pessimistic) mozilla1.0 nomination.
Keywords: mozilla0.9.2, mozilla1.0
Keywords: correctness
> I don't know what exactly is going on, but I guess, we run the recognition
> during SaveAsDraft. Will have to investigate more.

Looking at the saved Draft, it shows the HTML source of the msg with the tags
added by the recognizer. So, the problem here is most likely that
mozTXTToTHMLConverter::ScanHTML is ran during SaveAsDraft. This must not happen.
This function must only be called after the composition is finished.

Fixing bug 83425 would hide most of the results of this bug, but ScanHTML during
SaveAsDraft is still wrong, i.e. this bug is still valid.


A bad result of this bug: I just sent an SMTP session log to my provider. I
think you can guess what mess I actually sent out :-(.

I can't reproduce this bug anymore on a 0.9.2 branch build.
Ignore my last comment.
problem still occurs
Status: NEW → ASSIGNED
Keywords: mozilla0.9.2
Target Milestone: Future → mozilla0.9.7
I'm unable to reproduce this.  Regardless, moving to future.  If someone else
things this works, please mark wfm.
Target Milestone: mozilla0.9.7 → Future
> I'm unable to reproduce this.

The testcase has been fixed by another bugfix, which happens to work around this
bug. However, the underlying bug here still exists and is likely to appear in
other edge-cases. It is a bug in the code.
Product: MailNews → Core
Assignee: ducarroz → nobody
Status: ASSIGNED → NEW
QA Contact: esther → mime
Product: Core → MailNews Core

WFM on 68.0b5

Status: NEW → RESOLVED
Closed: 5 years ago
Priority: P3 → --
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.