Absolutely positioned objects with 'height': auto and 'top': and 'bottom': non-auto should not be content based

• Component: Layout and Rendering
• Status: RESOLVED FIXED

[Sam Weinig]

Absolutly positioned objects that have a value other than auto for 'top' and 'bottom' and a value of auto for 'height' should not compute the height to be based on the content (like is done if either or both of 'top' and 'bottom' are auto).  Instead the value should be calculated using the constraint equation for absolutely position objects.

[Sam Weinig]

Created attachment 8506 [details]
test case

[Sam Weinig]

Created attachment 8507 [details]
patch

Moves overflow code to after all the height calculations have been made for calcAbsoluteVertical and entirely removes it from the replaced version where it should never be used.  Also moves the calculation of containerheight and containerwidth to sepertate functions inorder to share the code.

[Sam Weinig]

Created attachment 8530 [details]
patch2

More targeted version of the patch.

[Maciej Stachowiak]

Created attachment 8569 [details]
another test case of interest

Hyatt mentioned that the bug in this additional test case is likely to be related. In this case, percentage height for a child of an absolute positioned element with height unspecified but top and bottom specified is not handled correctly.

[Sam Weinig]

Added bug 9137 to track the issue in maciej's test case.

[Dave Hyatt]

Comment on attachment 8530 [details]
patch2

r=me

[Beth Dakin]

I committed this patch.

[David Kilzer (:ddkilzer)]

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