Closed Bug 624 Opened 27 years ago Closed 23 years ago

child frames border settings override parent's

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect, P2)

Product:
Core
Component:
Layout: Images, Video, and HTML Frames
Type:
defect

Tracking

()

Status:
VERIFIED WONTFIX
Milestone:
Future

People

(Reporter: buster, Assigned: john)

References

(
URL
)

Details

(Keywords: testcase)

Attachments

(4 files)

inner document, used by testcase
(deleted), text/html
Details
reduced test case
(deleted), text/html
Details
oops, real reduced test case.
(deleted), text/html
Details
Simpler Testcase
(deleted), patch
Details | Diff | Splinter Review
<HTML><BODY BGCOLOR="Black" TEXT="White" LINK="#336699" VLINK="#33CC33" BACKGROUND="http://www.westwood.com/assets/background2.jpg" TOPMARGIN="nnn"> <TABLE> <TR><TD>x</TD> <TD VALIGN=TOP><IMG src="http://www.westwood.com//assets2/d2box.jpg" ALIGN="RIGHT" BORDER=0 WIDTH=124 HEIGHT=141></TD></TR></TABLE> </BODY> </HTML> you won't be able to view the page due to a jpeg bug.
Status: NEW → ASSIGNED
Component: Unknown → Style System
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
the d2box.jpg is showing, however the w_rotate1.gif is not (see under "downloads" on the far left) <A HREF="newindex.html" TARGET="_top"><IMG SRC="assets/w_rotate1.gif" WIDTH="87" HEIGHT="92" BORDER="0" VSPACE=5 ALIGN="top"></A>
Status: REOPENED → ASSIGNED
Assignee: kipp → karnaze
Status: ASSIGNED → NEW
As far as I can tell the images are loading right; given how flakey the netlib is, however, I'm not surprised if other people see different results. I'm reassigning to chris because there are 2 frameset layout bugs on the page. The left side bar is either too narrow or the right side section is too narrow, but there is a white gap between them. In addition, the right side (scrollable) section is too short by a few pixels.
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
QA Contact: 4110 → 1698
Although the component stated is 'Style System' this is an image related bug. Reassigning qa contact to elig@netscape.com
Target Milestone: M4 → M5
moving to M5.
Target Milestone: M5 → M6
Moving to M6
Moving to M8.
There are at least 2 problems remaining. Nav4.5 allows frameborder and/or border to override those settings in nested framesets. After Eric's upcoming checkin, this can be fixed. I checked in frameset regression tests (border1 thru border4) to use as a comparison to Nav4.5. The other problem is that the top right frame's document has too much spacing at the top and I'm not sure why. In general some of our documents have too much spacing at the top even when framesets are not involved.
Whiteboard: [Makingtest] csbooton@myna.com
Sounds simular to bug#7757 , it involves a problem with a background gif image not appearing. I made a testcase for that one.
Moving to M9.
Assignee: karnaze → pollmann
Status: ASSIGNED → NEW
Target Milestone: M9 → M10
What remains of this is frameset related. Reassigning to Eric and moving to M10.
Status: NEW → ASSIGNED
Summary: floating image doesn't render → child frames border settings should override parent's
After careful consideration, I've decided that I probably won't get this bug in for M12. Currently I have nearly 50 bugs scheduled for M13, so there is a possibility that this bug may need to be moved out farther still.
Gaw, this bug is still reproducible! Adding a test case...
Attached file inner document, used by testcase (deleted) —
Attached file reduced test case (deleted) —
Attached file oops, real reduced test case. (deleted) —
Component: Style System → HTMLFrames
OS: Windows NT → All
Hardware: PC → All
Summary: child frames border settings should override parent's → [4.x] child frames border settings override parent's
Target Milestone: M13 → M14
The interesting thing about this test case is that it shows that child frameset border settings *do* correctly over-ride parent's settings. we have: ... <FRAMESET ROWS="110,*" FRAMESPACING="0" BORDER=0 FRAMEBORDER="NO"> <FRAME SRC="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=3502"> <FRAMESET COLS="120,*" BORDER=10 FRAMEBORDER="NO"> ... The child frameset specified the border to be 10 pixels wide, which causes the gap to appear even though the parent specified the border to be 0 pixels. I'd say that the html of this page is flawed... However since Nav and IE both do not allow child framesets to over-ride the parent border settings, this is a compatability issue. Since this is a deprecated attribute anyway, we should probably aim for backwards compatability here, I'll see if I can break us to match IE and Nav. :)
Whiteboard: [Makingtest] csbooton@myna.com → [MAKINGTEST] csbooton@myna.com
Whiteboard: [MAKINGTEST] csbooton@myna.com → [TESTCASE]
Removing [MAKINGTEST] csbooton@myna.com. Emails to csbooton@myna.com bounce with user unknown. Marking [TESTCASE].
Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!
Keywords: testcase
Keywords: 4xp
Summary: [4.x] child frames border settings override parent's → child frames border settings override parent's
Whiteboard: [TESTCASE]
Minor and possibly invalid, moving to M17
Target Milestone: M14 → M17
Lowering priority, as this is not critical in relation to some of my other bugs. 1) major regressions 2) development blockers 3) crashers and major usability issues 4) cosmetic issues and standards compliance issues This falls in category 4 and is minor. Moving off to M20.
Severity: normal → minor
Target Milestone: M17 → M20
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: M20 → Future
QA Contact: elig → petersen
QA Contact update
QA Contact: petersen → amar
Bulk reassignin HTML FRAME/IFRAME bugs to Eric.
Assignee: pollmann → evaughan
Status: ASSIGNED → NEW
Bulk re-assigning all of Eric's HTMLFrame bugs to John.
Assignee: eric → jkeiser
WFM, 2002-03-12-08 (trunk) on Linux. The testcase, attachment 3592 [details], does not display any borders or gaps - which is the desired behaviour?
Attached patch Simpler Testcase (deleted) — — Splinter Review
If the problem is just that the child frameset's border attribute overrides the parent frameset's border attribute, then this is a testcase.
So yes, we *do* do this differently than Netscape 4.x and IE. And yes, we should. If someone wants to specify different borders for different parts of their framesets, who are we to deny them that? This is a feature. If you don't want your child frameset to have different borders, then don't specify a different border. WONTFIX.
Status: NEW → RESOLVED
Closed: 26 years ago → 23 years ago
Resolution: --- → WONTFIX
verified
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
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.

Attachment

General

Creator:
Created:
Updated:
Size: