Headers for RFC822 msgs not displayed in browser

RESOLVED WORKSFORME

Status

MailNews Core
MIME
P3
normal
RESOLVED WORKSFORME
18 years ago
10 years ago

People

(Reporter: BenB, Assigned: rhp (gone))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Reproduce:
Load <http://bugzilla.mozilla.org/showattachment.cgi?attach_id=6527> in the
browser.

Actual result:
You'll see the body only.

Expected result:
You'll see some headers and the body.

Additional Comments:
Not sure, how important that is.

Comment 1

18 years ago
It would also be good to be able to forward, reply to, or file the message.
It works for me. I see Subject, From, Date and To headers, nicely styled. I'm 
using a build that I pulled and built myself today.

(View Source does not work, however.)
(Reporter)

Comment 3

18 years ago
> It would also be good to be able to forward, reply to, or file the message.

Yes, this would help a lot with mailing list archives.

If we'll implement just the mentioned functionality, it shouldn't be too hard
with XUL and CSS2 (assuming, the fix I have in mind works). I could take this as
an enhancement bug.

However, all of the functionality (except "Move" of course) of a standalone msg
is potentially interesting. So, if we could load the msg in the soon-to-be
implemented standalone msg window (bug #10875), we'd have a decent solution and
would also fix this bug (and View Source). But I don't know, how hard this would
be to implement.
(Assignee)

Comment 4

18 years ago
Sorry guys...I'll make the headers reappear eventually...the rest can be help 
wanted.

- rhp
Status: NEW → ASSIGNED
Target Milestone: --- → M17
(Assignee)

Comment 5

18 years ago
Actually, this was another bug that I already fixed. This works fine in the
current tip build of the browser.

- rhp
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 6

18 years ago
Filed bug #34150 about the RFE.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.