Closed Bug 43464 Opened 25 years ago Closed 3 years ago

Frameset's don't redistribute extra children - frames not displayed.

Categories

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

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

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: 1212mozilla, Unassigned)

References

(
URL
)

Details

(Whiteboard: [nsbeta3-])

This site has never loaded correctly in mozilla. I never reported it because their frame set appears to invalid html. It is easy to edit the html for their site and come up with a working page, I even emailed them about it, but it hasn't been fixed. Tidy (html validator from w3c) complains mightily about the page. That being said, it does work under IE and Netscape, so it would probably be worth it to at least take a look at it.
Yep, the problem is right up front: <FRAMESET ROWS="70,*" FRAMEBORDER=NO FRAMESPACING=0 FRAMEPADDING=0 BORDER="0"> <FRAMESET COLS="100%"> <FRAME SRC="/ads/wwn-home.html" NAME="banner" MARGINHEIGHT=0 MARGINWIDTH=0 SCROLLING=NO NORESIZE> <FRAME SRC="main.html" NAME="story" MARGINHEIGHT=0 MARGINWIDTH=0 SCROLLING=AUTO NORESIZE> </FRAMESET> </FRAMESET> Since both frames are nested in the inner frameset, and the inner frameset only has one frame specified (100%), only one will display. This is a duplicate of an old bug. The problem is, the parser doesn't/can't look at the ROWS and COLS attribute of the frameset to correct this malformed case, and the logic in the frameset doesn't have the smarts to go grab children from siblings that have extras. CC'ing Harish because he probably remembers this one. This is really a frameset frame bug, and I have several solutions in mind (something like an overflow list for a frameset frame). Not sure this is a prominent site or common malformed case though, so marking Future (not nsbeta2 or nsbeta3) initially. If you disagree with the marking, please reopen and say why, thanks! BTW, to fix this site, just move up the first </FRAMESET> <FRAMESET ROWS="70,*" FRAMEBORDER=NO FRAMESPACING=0 FRAMEPADDING=0 BORDER="0"> <FRAMESET COLS="100%"> <FRAME SRC="/ads/wwn-home.html" NAME="banner" MARGINHEIGHT=0 MARGINWIDTH=0 SCROLLING=NO NORESIZE> </FRAMESET> <FRAME SRC="main.html" NAME="story" MARGINHEIGHT=0 MARGINWIDTH=0 SCROLLING=AUTO NORESIZE> </FRAMESET>
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Summary: Frame set does not load completly → Frameset's don't redistribute extra children - frames not displayed.
Target Milestone: --- → Future
Really CC'ing Harish this time instead of just saying I am. :) This is mainly just to see if you remember the old case as I do. Do you have an old dup of this lying around?
*** Bug 46605 has been marked as a duplicate of this bug. ***
*** Bug 48100 has been marked as a duplicate of this bug. ***
Nominating for Beta3. Granted the structure of the framesets are incorrect, they do rendered in Nav 4.7. There are at least three sites I have seen this problem with in N6(http://www.weeklyworldnews.com/, http://mp3.com.hk, and http:// www.macshowlive.com).
Keywords: nsbeta3
CC'ing ekrock
Marking nsbeta3-.
Whiteboard: [nsbeta3-]
*** Bug 55075 has been marked as a duplicate of this bug. ***
*** Bug 55802 has been marked as a duplicate of this bug. ***
QA Contact update
QA Contact: petersen → amar
*** Bug 85907 has been marked as a duplicate of this bug. ***
*** Bug 36334 has been marked as a duplicate of this bug. ***
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
Is this really something worth fixing?
FYI - I've seen a web site that may demonstrate this problem. http://www.gamesa.es/home_ingles.htm It includes HTML like this. <frameset rows="31,*,25" frameborder="NO" border="0" framespacing="0" vspace="0" hspace="0" marginwidth="0" marginheight="0"> <frame name="framesuperior" scrolling="NO" noresize src="frame_superior_ingles.htm" frameborder="0" marginlength="0" marginwidth="0"> <frame name="framecontenido" scrolling="NO" noresize src="cont_home_layers_ingles.htm" frameborder="0" marginlength="0" marginwidth="0"> <frame name="frameinferior" scrolling="NO" noresize src="frame_inferior_ingles.htm" frameborder="0" marginlength="0" marginwidth="0"> </frameset> <noframes> </noframes>
No, that site has nothing to do with this bug.... And even if it did, that wouldn't exactly be relevant to the bug, since we know what the "problem" is.
QA Contact: amar → layout.html-frames
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
Assignee: john → nobody
Severity: minor → S4

The severity field for this bug is relatively low, S4. However, the bug has 6 duplicates.
:emilio, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(emilio)

I reported this bug 23 years ago and the last duplicate was recorded 22 years ago. I went through six sites given as examples in this bug report and the duplicates. Four of them are defunct and two of them have been updated and work fine now. I personally haven't run across a site with this problem in over twenty years. Rather than raising the priority, I'm closing this bug as WONTFIX. It isn't worth anybody's time to put in a workaround for badly crafted framesets.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX

Thanks :)

Flags: needinfo?(emilio)

FYI, here's an example of an old site demonstrating the problem from archive.org:

https://web.archive.org/web/20040612084916/https://www.princeton.edu/~jedwards/cif/intro.html

I agree, no need to fix that.

You need to log in before you can comment on or make changes to this bug.