Open Bug 82280 Opened 23 years ago Updated 2 years ago

Use iframe or object tags for inlined parts in a mail message

Categories

(MailNews Core :: MIME, defect)

defect

Tracking

(Not tracked)

People

(Reporter: mscott, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

This bug stems from Bug #77539. 

Currently the BASE tags being generated by libmime for inlined images aren't
being honored. This is due to the whacky html mime emits where each inlined part
is wrapped in it's own html & body tags. 

We need a special kind of iframe (80713) which scrolls against an outer iframe.
Then each inlined part could be in it's own iframe with it's own BASE tag.
adding dependency on special iframe object. 
Status: NEW → ASSIGNED
Depends on: 80713
Target Milestone: --- → mozilla0.9.2
adding pdt+
Whiteboard: [PDT+]
Priority: -- → P2
since 80713 isn't targeted until mozilla 1.0, then we probably need to push this
bug off till then as well since I can't fix this without the work in 80713. 

The cost to .9.2 is that base urls won't work in mail messages. Probably not
tragic and we can ship with it if we have to so I'm going to push this out to be
in sync with the layout bug. 
Target Milestone: mozilla0.9.2 → mozilla1.0
Bug 80713 is targeted at 1.0 arbitrarily. If we end up needing this fixed
sooner, we can divert our attention to it.

mscott, per your comments, I'll move this off PDT+ in the status whiteboard, ok?
 This means that clicking on a particular type of URL in mail messages won't
work, right?  Do you know how common base URLs are?
Whiteboard: [PDT+]
Target Milestone: mozilla1.0 → mozilla1.2
Also see http://www.theregister.co.uk/2004/07/30/email_privacy/ regarding the
seriour danger of iFRAMES
Product: MailNews → Core
Blocks: 183726
xref bug 341059.
OS: Windows 2000 → All
Hardware: PC → All
Assignee: mscott → nobody
Status: ASSIGNED → NEW
QA Contact: esther → mime
Product: Core → MailNews Core
Priority: P2 → --
Target Milestone: mozilla1.2alpha → ---
Blocks: 31052
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.