Closed Bug 212960 Opened 22 years ago Closed 22 years ago

size of box with relative positioning inside a table is not calculated as needed

Categories

(Core :: Layout: Positioned, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: bergers, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 Galeon/1.0.2 (X11; Linux i686; U;) Gecko/0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030507 The example page (http://www.cip.informatik.uni-muenchen.de/~bergers/testWidthRelAbs.html) contains a relative positioned DIV inside a tablecell (and is therefore collapsed as small as possible, which is OK). This DIV contains another DIV with absolute positioning. The latter DIV should be taken into account for width calculation of former DIV, according to "10.3.7 Absolutely positioned, non-replaced elements" in the W3C standard (http://www.w3.org/TR/REC-CSS2/visudet.html#abs-non-replaced-width). It looks like if the behaviour for calculation of width and height are separated. I did not investigate the behaviour of the height, therefore it is set to a fixed value in the example. The width seems to be calculated correctly in Mozilla-1.2.1 (maybe even earlier) until Mozilla-1.3a. I found the Bug in Mozilla-1.3b and Mozilla-1.4b. Reproducible: Always Steps to Reproduce: 1. look at http://www.cip.informatik.uni-muenchen.de/~bergers/testWidthRelAbs.html Actual Results: The yellow box is too small (as large as the first line of text. By the way: without the first line the yellow box would collapse to zero width and would not be visible at all) Expected Results: The yellow box should be as large as the second line of text
> The latter DIV should be taken into account No, it should not. Absolutely positioned elements are taken out of flow and do not affect layout of any ancestors in any way. Mozilla up to 1.2.1 had a bug in which table cells _did_ take absolutely positioned elements into account, but that was fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.