214708 - CSS2 layout is not displaying properly - parent/child relationship problems

Status: RESOLVED INVALID

(Core :: Layout: Block and Inline, defect)

Description

[John Douglas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

Nested block elements act more like siblings, as the parent element is not
properly expanding.  CSS2 validates, and it appeared fine until Moz 1.4.  Net

If you visit the site using IE5.5+ or the previous build of Netscape (6.2.1),
and compare it to the latest moz 1.4, you wil see that:
1- the contact info element on the navigation is being improperly positioned
2- the main content element (which has a brown background) is not expanding in
height to match the length as determined by the child-elements it contains

Reproducible: Always

Steps to Reproduce:
1.Go to www.likelola.com using moz 1.4 and you'll see the problem
2.
3.

Actual Results:  
The page displays incorrectly

Expected Results:  
The page should display correctly

i designed this site very recently, using ie5.5, ie6 and netscape 6.2.1.  the
css2 layout methods i used acted in very similiar ways across each browser.  it
is only in moz1.4 that my methods are not acting in similiar fashion.

the direct link to the style sheets are
http://www.likelola.com/ie_style.css
http://www.likelola.com/ns_style.css

Comment 1

[Jesiah S]

floats are not considered in the height of DIVS.  There are two ways to avoid
this  1. don't float your divs
2. add <BR style="clear:both"> after your floated divs.

Comment 2

[John Douglas]

Can you please point me to the specification that shows floats are not 
considered in the height of DIVS?

Comment 3

[Jesiah S]

http://www.w3.org/TR/CSS21/visudet.html#q19

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

IE/Windows basically has two totally different implementations of 'display:
block' -- you get the second one, which expands to hold floats, if you set
'width' or 'height' or 'position' to something other than their defaults.

I also don't see the problems in the page, so I'm guessing it's been fixed.