Closed Bug 335333 Opened 15 years ago Closed 15 years ago
[FIX]Relative, remote images which have a Content-Base fail to display
Summary: Relative, remote images which have a Content-Base fail to display. This probably won't end up in MailNews:Backend as it is currently, but just filing here for now... Regression Range: Between 2006-04-10-07 and 2006-04-11-10, relative image URIs aren't being resolved nor displayed. Steps to Reproduce: 1. Go to http://www.iusb.edu 2. In Suite, do a File | Send Page 3. View the mail message (click the "Not a Scam" button and show remote images, if prompted) Expected Results: Relative-pathed images such as <img src="foo/bar.gif"> should display, since the message includes both Content-Base and Content-Location fieldsets. Actual Results: No relative images display. The message's HTML content setup is something like this: Content-Type: text/html; charset=ISO-8859-1; name="www.iusb.edu/" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="www.iusb.edu/" Content-Base: "http://www.iusb.edu/" Content-Location: "http://www.iusb.edu/" The actual URI is like: <img src="img/topnav-right.gif">
This is a regression from bug 321299
Assignee: nobody → general
Component: MailNews: Backend → DOM: Core
OS: Windows XP → All
Priority: -- → P1
QA Contact: ian
Hardware: PC → All
Summary: Relative, remote images which have a Content-Base fail to display. → [FIX]Relative, remote images which have a Content-Base fail to display.
Target Milestone: --- → mozilla1.9alpha
Need to not lose our baseHref property when we get inserted into the document.
Comment on attachment 219713 [details] [diff] [review] Fix Yeah, duh. r+sr=jst
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Verified FIXED using build 2006-04-25-18 of SeaMonkey trunk on Windows XP. Thanks for the quick turnaround, Boris!
Status: RESOLVED → VERIFIED
This is blocking if bug 321299 is
Flags: blocking184.108.40.206? → blocking220.127.116.11+
Comment on attachment 219713 [details] [diff] [review] Fix approved for 1.8.0 branch, a=dveditz for drivers
Attachment #219713 - Flags: approval18.104.22.168? → approval22.214.171.124+
Comment on attachment 219713 [details] [diff] [review] Fix Unapproving for 126.96.36.199 and moving to next release per bug 321299 comment 36
Comment on attachment 219713 [details] [diff] [review] Fix Jonas says we'll get a combined branch patch for all the related regressions.
Moving to 188.8.131.52 to follow bug 321299
If bug 321299 is blocking 1.8.1 then this should be also.
Flags: blocking1.8.1? → blocking1.8.1+
Target Milestone: mozilla1.9alpha → mozilla1.8.1beta2
Jonas, was this fixed on the branch(es) by bug 321299?
Target Milestone: mozilla1.8.1beta2 → mozilla1.8.1
This was fixed by bug 321299 on the 1.8 branch.
Target Milestone: mozilla1.8.1 → mozilla1.9alpha
I checked a combined patch into the 1.8.0 branch.
verified per comments in 321299 from Blakes comment #13
You need to log in before you can comment on or make changes to this bug.