Closed
Bug 102865
Opened 24 years ago
Closed 24 years ago
background left side banner image is overlapped by table
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: mozbugz, Assigned: attinasi)
References
()
Details
(Keywords: verifyme)
Attachments
(6 files)
grey banner (background image file) on the left is not even displayed in ns6.1
and displayed properly in
IE6 and it is only partially displayed in current nightlies on W2K. so its
suppose to show the whole grey storagereview banner as part of body frame, but
doesn't.
this is not a problem on other pages of the site. I see the renderer correct
until, then at the last second the whole table (not sure if table here or not
source hard to come by?) gets shifted left overtop the image. There is a small
spacer image (buffer.gif grey in color see attached shot taken in ns6.1).
| Reporter | ||
Comment 1•24 years ago
|
||
| Reporter | ||
Comment 2•24 years ago
|
||
site using doc type declaration here:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
| Reporter | ||
Comment 3•24 years ago
|
||
*** Bug 102337 has been marked as a duplicate of this bug. ***
Comment 4•24 years ago
|
||
Confirming with fresh Linux CVS-I see the top frame overlapping the top part of
the page (I only see the lower half of one of the grey buttons on the right).
Status: UNCONFIRMED → NEW
Component: Layout → HTMLFrames
Ever confirmed: true
| Assignee | ||
Comment 5•24 years ago
|
||
When I pull the source for the body frame and load it by itself, it is fine.
When it is part of the frameset, the left-edge banner is cut off. I'll attach
the source for the main body frame now...
Status: NEW → ASSIGNED
| Assignee | ||
Comment 6•24 years ago
|
||
| Assignee | ||
Comment 7•24 years ago
|
||
| Assignee | ||
Comment 8•24 years ago
|
||
| Assignee | ||
Comment 9•24 years ago
|
||
Page looks fine when the frames are all served up from Bugzilla (or locally).
Strange, maybe there is a timing issue with the server?
I cannot get the site to server up just he body frame's page, so I'm not sure
how that will look by itself off of their server.
CC'ing karnaze for the table-foo.
| Reporter | ||
Comment 10•24 years ago
|
||
see bug 98687 for info on loading body source pages.. I believe after sending an
email to webmaster, it was taken offline and doesn't allow just loading of pages
by themselves, mostly a JS, CSS loading problem.
| Reporter | ||
Comment 11•24 years ago
|
||
| Reporter | ||
Comment 12•24 years ago
|
||
opps should have entered plain text for that last attachment for .html to see
the source like the view source document, correct?, as it comes out I see as the
same attachment that Mark added for main body frame source (base href added).
sorry, didn't figure that was going to happen.
| Assignee | ||
Updated•24 years ago
|
Attachment #52006 -
Attachment mime type: text/html → text/text
| Assignee | ||
Updated•24 years ago
|
Attachment #52006 -
Attachment mime type: text/text → text/plain
| Assignee | ||
Comment 13•24 years ago
|
||
Updated the mime type for ya.
| Reporter | ||
Comment 14•24 years ago
|
||
source for this index.jsp with problem page:
<body bgcolor="#ffffff" marginheight="0" marginwidth="0"
topmargin="0" leftmargin="0" rightmargin="0"
link="#000080" vlink="#000080" alink="#800000">
<table border="0" cellspacing="0" cellpadding="0" width="100%"
align="center"><tr><td width="1%" valign="top"
background="images/sideline.gif"><img border=0 src="images/buffer.gif"
width="35" height="5" alt=""></td><td width="99%"><table border="0" width="97%"
align="center"><tr><td>
source from main news.html that doesn't exhibit problem page:
<body BGCOLOR="#FFFFFF" LEFTMARGIN="0" TOPMARGIN="0" MARGINWIDTH="0"
MARGINHEIGHT="0">
<table BORDER="0" CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<tr><td WIDTH="1%" VALIGN=TOP BACKGROUND="/images/sideline.gif"><img BORDER="0"
SRC="/images/buffer.gif" WIDTH=35 HEIGHT=5 ALT=""></td>
<td WIDTH="2%" VALIGN=TOP>
<body BGCOLOR="#FFFFFF" LEFTMARGIN="0" TOPMARGIN="0" MARGINWIDTH="0"
MARGINHEIGHT="0">
<table BORDER="0" CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<tr><td WIDTH="1%" VALIGN=TOP BACKGROUND="/images/sideline.gif"><img BORDER="0"
SRC="/images/buffer.gif" WIDTH=35 HEIGHT=5 ALT=""></td>
<td WIDTH="2%" VALIGN=TOP>
| Reporter | ||
Comment 15•24 years ago
|
||
opps, got a double source paste there on the second one.
| Reporter | ||
Comment 16•24 years ago
|
||
I am curious to weather there is a difference in the way mozilla renders the two
pages based upon the way the source is coded with=# or with="#".. and the
ordering of element variables on the code parser..
| Reporter | ||
Comment 17•24 years ago
|
||
frameset header is using the doctype I had placed above... while in the frameset
for the news.html page and others.. is:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
while the page in question here, is not using a doctype for the body frame page:
so it is rendered in quirks-mode then, correct?
| Reporter | ||
Comment 18•24 years ago
|
||
let me clarify that the header for the frameset is using the following doctype:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">
while the body of the frame is different or None as my previous comment..
| Reporter | ||
Comment 19•24 years ago
|
||
| Reporter | ||
Comment 20•24 years ago
|
||
is it possible that changes to bug 102344 fixed this, because the page works in
build 2001100610 W2K and it finally displays correctly.. cool!
| Reporter | ||
Comment 21•24 years ago
|
||
I'd say this is fixed! anyone wanna change it?
| Reporter | ||
Comment 22•24 years ago
|
||
funny, now it works in ns6.1 too and other mozilla builds.. i'd say wfm instead.
| Assignee | ||
Comment 23•24 years ago
|
||
WFM based on reporters comments.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 24•24 years ago
|
||
Marking this big verified according to the reporter comments
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Product: Core → Core Graveyard
Updated•7 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•