82852 - [FLOAT]Wrong height for Rel Pos OR floated block containing Float

Status: RESOLVED DUPLICATE of bug 180711

(Core :: Layout, defect)

Description

[Val Sharp]

From Bugzilla Helper:
User-Agent: Mozilla/4.6 [en-gb]C-CCK-MCD NetscapeOnline.co.uk  (Win98; I)
BuildID:    2001050515

In computing heights and margins of block-level, non-replaced elements in normal 
flow, http://www.w3.org/TR/REC-CSS2/visudet.html#q17 says:

  "Only children in the normal flow are taken into account (i.e., floating boxes 
and absolutely positioned boxes are ignored, and relatively positioned boxes are 
considered without their offset)."

Reproducible: Always
Steps to Reproduce:
The attached testcase shows that the height of the float is wrongly being 
included in the computation of the height of the Rel Pos containing block.

Comment 1

[Val Sharp]

Attachment: Testcase - wrong height for Rel Pos block containing Float

Comment 2

[Chris Petersen]

Chnaging QA Contact

Comment 3

[Keyser Sose]

Marking NEW.
I see this in the 0.9.2 release.

Comment 4

[karnaze (gone)]

Reassigning to attinasi.

Comment 5

[Kevin McCluskey (gone)]

Still a problem with 11/02/2001 CVS build on WINNT.
Adding [FLOAT] to status.

Comment 6

[Kevin McCluskey (gone)]

Moved FLOAT to Summary

Comment 7

[Eric A. Meyer (dead account)]

I stumbled across this bug and discovered it's not restricted to relatively
positioned elements, but also those than have been floated-- so I've updated the
summary accordingly.  I'll also attach a testcase demonstrating the problem.

Comment 8

[Eric A. Meyer (dead account)]

Attachment: Testcases showing incorrect height on elements containing floats

It turns out that if you float or relatively position an element that contains
floats, the "outer" element will wrap around the floats.  This should not
happen.

Comment 9

[Eric A. Meyer (dead account)]

Correcting misleading typo in summary change.  Apologies for the spam.

Comment 10

[Eric A. Meyer (dead account)]

Thanks to input from a student in one of my CSS classes, I've come up with
another testcase (well, a small set of them) showing weirdness with floated
eimages inside relatively-positioned block-level elements, and how the float
basicalyl gets ignored for later flow.  Even worse, adding borders to elements
can throw off the layout from one wrong state to another.  Ick.  I also have a
case of a relatively-positioned elemennt expanding itself to wrap around a tall
float, even though there's no apparent reason why it should.

CC:ing my favorite CC: buddy, dbaron.  Testcase to follow shortly.

Comment 11

[Eric A. Meyer (dead account)]

Attachment: Various float-and-flow problems in relatively-positioned elements

Comment 12

[Boris Zbarsky [:bzbarsky]]

*** Bug 177685 has been marked as a duplicate of this bug. ***

Comment 13

[Boris Zbarsky [:bzbarsky]]

Fixed by bug 180711

*** This bug has been marked as a duplicate of 180711 ***