Closed Bug 227642 Opened 22 years ago Closed 22 years ago

iframes don't render

Categories

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

x86
Windows 2000
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 225037

People

(Reporter: mark.slater, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Firebird/0.7+ (Oxs G7 SSE optimized) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Firebird/0.7+ (Oxs G7 SSE optimized) The URL (www.newstoday.com) has three iframes, one for main news, one for user-submitted news, and the third holds a forum. With recent nightlies, FB only renders the first (main news) including the flash controls for that iframe, and seemingly ignoring the other two. Reproducible: Always Steps to Reproduce: 1. Visit site Actual Results: Site rendered, no crashes, but missing two iframes Expected Results: Display the site with ALL iframes showing. Had a look at the source of that site and didn't see anything out of the ordinary. (I'm also using an unofficial 'optimized' version of Firebird, tho I don't think that should have any impact on the rendering engine)
Component: General → Layout: Tables
Product: Firebird → Browser
Version: unspecified → Trunk
Assignee: blake → table
-> Browser, HTML Frames.
Assignee: table → frame
Component: Layout: Tables → Layout: HTML Frames
Line 15 of http://www.newstoday.com/docs/contentarea.html : body { overflow:hidden; } All the children of body are positioned resulting in a zero height body and then the above rule makes us clip everything. As I said in bug 225037 comment 2, the current behaviour does not make much sense, there must be a better way of doing this and still be compliant... *** This bug has been marked as a duplicate of 225037 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
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.