Closed
Bug 335333
Opened 19 years ago
Closed 19 years ago
[FIX]Relative, remote images which have a Content-Base fail to display.
Categories
(Core :: DOM: Core & HTML, defect, P1)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
FIXED
mozilla1.9alpha1
People
(Reporter: stephend, Assigned: bzbarsky)
References
Details
(Keywords: regression, verified1.8.0.7, verified1.8.1, Whiteboard: regression from 321299)
Attachments
(1 file)
3.54 KB,
patch
|
jst
:
review+
jst
:
superreview+
dveditz
:
approval-branch-1.8.1-
dveditz
:
approval1.8.0.4-
dveditz
:
approval1.8.0.5-
|
Details | Diff | Splinter Review |
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">
Assignee | ||
Comment 1•19 years ago
|
||
This is a regression from bug 321299
Assignee: nobody → general
Blocks: 321299
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
Assignee | ||
Comment 2•19 years ago
|
||
Need to not lose our baseHref property when we get inserted into the document.
Assignee: general → bzbarsky
Status: NEW → ASSIGNED
Attachment #219713 -
Flags: superreview?(jst)
Attachment #219713 -
Flags: review?(jst)
Comment 3•19 years ago
|
||
Comment on attachment 219713 [details] [diff] [review]
Fix
Yeah, duh. r+sr=jst
Attachment #219713 -
Flags: superreview?(jst)
Attachment #219713 -
Flags: superreview+
Attachment #219713 -
Flags: review?(jst)
Attachment #219713 -
Flags: review+
Assignee | ||
Comment 4•19 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•19 years ago
|
||
Verified FIXED using build 2006-04-25-18 of SeaMonkey trunk on Windows XP.
Thanks for the quick turnaround, Boris!
Status: RESOLVED → VERIFIED
Updated•19 years ago
|
Flags: blocking1.8.0.4?
Updated•19 years ago
|
Attachment #219713 -
Flags: approval1.8.0.4?
Updated•19 years ago
|
Whiteboard: regression from 321299
Comment 6•19 years ago
|
||
This is blocking if bug 321299 is
Flags: blocking1.8.0.4? → blocking1.8.0.4+
Comment 7•19 years ago
|
||
Comment on attachment 219713 [details] [diff] [review]
Fix
approved for 1.8.0 branch, a=dveditz for drivers
Attachment #219713 -
Flags: approval1.8.0.4? → approval1.8.0.4+
Updated•19 years ago
|
Attachment #219713 -
Flags: approval-branch-1.8.1+
Updated•19 years ago
|
Flags: blocking1.8.0.5?
Flags: blocking1.8.0.4-
Flags: blocking1.8.0.4+
Comment 8•19 years ago
|
||
Comment on attachment 219713 [details] [diff] [review]
Fix
Unapproving for 1.8.0.4 and moving to next release per bug 321299 comment 36
Attachment #219713 -
Flags: approval1.8.0.5?
Attachment #219713 -
Flags: approval1.8.0.4-
Attachment #219713 -
Flags: approval1.8.0.4+
Attachment #219713 -
Flags: approval-branch-1.8.1?
Attachment #219713 -
Flags: approval-branch-1.8.1+
Updated•19 years ago
|
Flags: blocking1.8.0.5? → blocking1.8.0.5+
Comment 9•19 years ago
|
||
Comment on attachment 219713 [details] [diff] [review]
Fix
Jonas says we'll get a combined branch patch for all the related regressions.
Attachment #219713 -
Flags: approval1.8.0.5?
Attachment #219713 -
Flags: approval1.8.0.5-
Attachment #219713 -
Flags: approval-branch-1.8.1?
Attachment #219713 -
Flags: approval-branch-1.8.1-
Comment 10•19 years ago
|
||
Moving to 1.8.0.6 to follow bug 321299
Flags: blocking1.8.0.6+
Flags: blocking1.8.0.5-
Flags: blocking1.8.0.5+
Comment 11•19 years ago
|
||
If bug 321299 is blocking 1.8.1 then this should be also.
Flags: blocking1.8.1?
Updated•19 years ago
|
Flags: blocking1.8.1? → blocking1.8.1+
Target Milestone: mozilla1.9alpha → mozilla1.8.1beta2
Comment 12•18 years ago
|
||
Jonas, was this fixed on the branch(es) by bug 321299?
Target Milestone: mozilla1.8.1beta2 → mozilla1.8.1
Comment 13•18 years ago
|
||
This was fixed by bug 321299 on the 1.8 branch.
Updated•18 years ago
|
Keywords: fixed1.8.1
Assignee | ||
Updated•18 years ago
|
Target Milestone: mozilla1.8.1 → mozilla1.9alpha
You need to log in
before you can comment on or make changes to this bug.
Description
•