Closed
Bug 141666
Opened 23 years ago
Closed 15 years ago
Option to override content-type and view plain text message as HTML
Categories
(SeaMonkey :: UI Design, enhancement)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: hEADcRASH, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
Sometimes i would like to open an eMail that contains HTML code in my browser
(as a lot of eMail clients don't render it correctly). However, when i drop it
on Mozilla, it is just rendered as plain text, unless i strip off the header.
However, Internot Exploder will render the header as text, but then render the
text following the <html> tag as a web page. Any chance that Mozilla could do
this as well? Please see the attached file as an example.
|
||
Comment 2•23 years ago
|
||
to XP apps to decide what to do with a badly malformed mail file that gets
dropped on us....
Assignee: Matti → sgehani
Component: Browser-General → XP Apps
QA Contact: imajes-qa → paw
|
||
Updated•22 years ago
|
Status: UNCONFIRMED → NEW
Depends on: 11521
Ever confirmed: true
OS: MacOS X → All
Hardware: Macintosh → All
Summary: Could a text file containing HTML code be rendered even if there is a "header?" → Option to override content-type and view plain text message as HTML
|
|
||
Comment 3•22 years ago
|
||
*** Bug 202760 has been marked as a duplicate of this bug. ***
|
||
Comment 4•22 years ago
|
||
My example (http://bugzilla.mozilla.org/show_bug.cgi?id=202760) comes from a
totally different context (index.jsp for tomcat), so if you leave mine as
duplicate, the summary probably should not just reference "messages", but
"arbitrary non-html" files - be it text-plain or even xml or whatever MIME-type
that is not rendered as HTML.
Yet another related one --> http://bugzilla.mozilla.org/show_bug.cgi?id=191000
|
||
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
|
||
Updated•16 years ago
|
Assignee: samir_bugzilla → nobody
QA Contact: pawyskoczka → ui-design
|
|
||
Comment 5•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
|
|
||
Comment 6•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•