Closed Bug 72232 Opened 24 years ago Closed 23 years ago

Forwarding an html page is not rendered correctly whnereceived

Categories

(MailNews Core :: Composition, defect, P2)

x86
All

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.1

People

(Reporter: sheelar, Assigned: bugzilla)

References

Details

(Whiteboard: [nsbeta1+])

Attachments

(1 file)

buildid: 2001-03-15-14 on win98 buildid: 2001-03-16-08 on mac 2001-03-14-21 on linux steps to reproduce: Send this page http:\\bugzilla.mozilla.org/show bug.cgi?id=70928 from the browser After receiving this you will see the page displayed inline and the page is rendered correctly Click on forward button from the toolbar and send this to yourself Actual result: The forwared page displays html tags and the page is not rendered the way it was sent initially. Expected result: forwarded mail when received should display the page correctly
cc esther, putterman, change qa contact to myself, Nominating this bug for nsbeta1 since forwarding a html page and after received should be rendered as a page. Sorry I missed typed the link below. Just go to bug 70928 send page on that bug and after receiving this page, forward it to yourself and you should see the problem when you tried to see this forwarded message.
Keywords: nsbeta1
QA Contact: esther → sheelar
Checked on the recent build: 2001-03-21-08 on win98. This seems to happen only when forwarding a bugzilla page. I forwared www.yahoo.com home page and this displayed fine inline.
marking nsbeta1+ and moving to mozilla0.9.1
Priority: -- → P2
Whiteboard: [nsbeta1+]
Target Milestone: --- → mozilla0.9.1
Forward as attchment works fine. However I can see the problem when forwarding inline.
Status: NEW → ASSIGNED
Summary: Forwarding an html page is not rendered correctly when received → Forwarding an html page is not rendered correctly whnereceived
the problem occurs only with page with the url is a cgi address. We failed to detect the mime type of the attachment!
*** Bug 76627 has been marked as a duplicate of this bug. ***
I've seen this problem with just an attachment which is a status report (w/out any cgi script or anything like that).
Whiteboard: [nsbeta1+] → [nsbeta1+] I am working on it...
Whiteboard: [nsbeta1+] I am working on it... → [nsbeta1+]Have fix
Attached patch Proposed fix, v1 (deleted) — Splinter Review
mscott think that the unknown decoder should have been called before nsURLFetcher get called an this has regressed. Therefore my patch might not be the right one!
r=varada- ( but why is the unknown converter/decoder not run auto?) if mscott is ok with this then ok.
sr=mscott
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Whiteboard: [nsbeta1+]Have fix → [nsbeta1+]
Fixed and checked in. I am pretty sure that will fix other bug when we generate a bogus content type.
verified, 2001052211-win98 2001052208-linux 2001052210-mac forwarded bugzilla page, ccn web page using->different menu items(file menu item message|forward|, message|forwardas->inline, context menu in thread pane.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: