67543 - Position of abs pos element within floated rel pos containing block is incorrect. [ABS POS] [REL POS]

Status: RESOLVED DUPLICATE of bug 210873

(Core :: Layout, defect, P4)

Description

[Val Sharp]

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

An Absolutely Positioned element with offsets specified, e.g. 'top' and/or 
'left', will not recognise a block which is both Relatively Positioned and 
Floated as its containing block. 

However, if the Absolutely positioned element has no offsets specified, i.e. 
auto, then it does use the relatively positioned floated block as its containing 
block.


Reproducible: Always
Steps to Reproduce:
The attached testcase illustrates both these situations:

Example 1 shows the Absolutely Positioned element with 'top:0px; left:0px' 
wrongly positioned outside the containing block.

Example 2 shows that the Absolutely Positioned element, with neither 'top' nor 
'left' specified, is properly contained within its containing block.

Examples 3 & 4 are the same as Examples 1 & 2, except the containing block is 
only Relatively Positioned, not Floated, showing that it's the use of Float in 
the containing block that causes the problem.


Expected Results:  The position of the absolutely positioned element should be 
calculated with respect to its containing block, even if that block is floated.

Comment 1

[Val Sharp]

Attachment: Floated containing block - testcase

Comment 2

[Hixie (not reading bugmail)]

Nice test case!!!

Comment 3

[Marc Attinasi]

Accepting.

Comment 4

[Marc Attinasi]

Milestone set: Moz 1.0

Comment 5

[Marc Attinasi]

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

Comment 6

[Mats Palmgren (inactive)]

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

Comment 7

[André Dahlqvist]

Not limited to Windows. OS->All.

Comment 8

[Greg K.]

Reconfirmed using FizzillaCFM/2002071208. Setting Platform=All.

Comment 9

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

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