Closed
Bug 110533
Opened 23 years ago
Closed 23 years ago
HTML signature file displays as html entities
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: marina, Assigned: bugzilla)
References
Details
(Keywords: regression)
*** observed with 2001-11-16-03 build ***
Steps to repro:
- create an html file;
- on the account settings indicate it as a signature file;
- open new mail composition;
//note: the html file displays as html entities, plain ytext signature is OK
Keywords: regression
|
||
Comment 1•23 years ago
|
||
I see this too. Yuck.
|
||
Comment 2•23 years ago
|
||
This is very bad; it breaks HTML mail functionality -- bumping up severity.
Severity: normal → critical
|
|
||
Comment 3•23 years ago
|
||
Investigated this and this regressed because in nsMsgCompose::ProcessSignature()
when we look up if this is a HTML file, we fail because
nsStandardURL::SetFilePath() is not implemented.
So this bug will probably be fixed when darin fixes that.
Severity: critical → major
Depends on: 110500
|
||
Updated•23 years ago
|
QA Contact: sheelar → esther
|
Assignee | |
Comment 4•23 years ago
|
||
HTML signature are working fine using today's debug build on Win2K. Even using
non-ascii characters. WFM
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
this is fine with my current trunk builds
Status: RESOLVED → VERIFIED
|
||
Updated•20 years ago
|
Product: MailNews → Core
|
||
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•