You need to
before you can comment on or make changes to this bug.
Sub-elements set to 100% width and height do not properly resize with parents if the parent element has min-width/height applied via CSS. Removal of the min-width/height specification returns resizing to normal.
This situation does not occur in Firefox 220.127.116.11 or in IE 7. This occurs in Safari 3.1.1 (10.5, Win XP) and Webkit nightly r32416 (10.5).
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta name="generator" content="BBEdit 8.7">
border: 1px black solid;
Created an attachment (id=20792) [details]
This is a test-case for the bug. Start the window out small, load, then increase its size. Sub-element will not increase.
Created an attachment (id=20793) [details]
Correct test case
The previous test case had a typo. It removed the min-x attribute making it work. This attachment should demonstrate the problem.
Created an attachment (id=123614) [details]
Testcase for min-height with html and body
I recently ran into this problem when adding size styles to html and body. The min-width problem (but not the min-height problem) seems to have been fixed since this bug was posted, and the behavior is different depending on whether the elements being styled are html and body. This attachment demonstrates the problem for html and body. Firefox handles this situation correctly.
Created an attachment (id=123616) [details]
Testcase for min-height and min-width with other elements
Here's a testcase for min-height and min-width using divs instead of html and body. The min-width behavior appears to be completely correct. The min-height behavior matches Firefox in this case, but it still appears the be wrong (the element with class="body" should expand to fill the element with class="html", but appears to be sizing to enclose its child element instead, for some reason). IE9 has the same behavior as Firefox for both of these testcases.
I just realized that I'm not having the same problem that this bug was about, although it's triggered under approximately the same conditions. I'll file a separate bug.