548 bytes, text/html
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:220.127.116.11) Gecko/20100106 Ubuntu/9.10 (karmic) Firefox/3.5.2 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:18.104.22.168) Gecko/20100106 Ubuntu/9.10 (karmic) Firefox/3.5.2 When setting a max-height in a parent element, it's children don't get this value of height, for example when setting a percentage value for max-height on this elements children. See the test case for an example. Looking at the W3 (http://www.w3.org/TR/CSS21/visudet.html), it says: "If the height of the containing block is not specified explicitly (i.e., it depends on content height), and this element is not absolutely positioned, the percentage value is treated as '0' (for 'min-height') or 'none' (for 'max-height')." The issue I see here is how the term "explicitly" is defined, I would say that when a max-height rule has been set and is in effect, then the height of the containing block is explicitly set, as it no longer depends on the height of the content, though just with this, I can see that it can be argued that explicitly means setting the height attribute. Reproducible: Always Steps to Reproduce: 1. Load the test case as in my next post Actual Results: Image displayed with its full height of 595px. Expected Results: The image to have been scaled so that it had a height of 270px (90% of 300px)
Keywords: css2, testcase
Hardware: x86 → x86_64
Version: unspecified → 3.5 Branch
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.