Closed
Bug 223680
Opened 21 years ago
Closed 21 years ago
DIV's positionioned incorrectly, when the contents of a div changes it's fixed height.
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
VERIFIED
INVALID
People
(Reporter: kevinar18, Unassigned)
Details
(Keywords: testcase)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031023 Firebird/0.7+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031023 Firebird/0.7+ If you set a div tag with a fixed height, and then it's contents are such that they cause the div height to increase, this causes Mozilla to incorrectly render other elements on the page in the wrong location. Reproducible: Always Steps to Reproduce: 1. Put two relative divs on a page. 2. Make the first div a fixed height of 1px 3. Put something inside that first div (such as text). Actual Results: What occurs is that second div covers up the first div. In other words, Mozilla still thinks that the first div is 1px in height, when it has actually increased in height due to the contents of the div. Thus, Mozilla incorrectly positions the second div in the wrong place (over the top of the first div). Expected Results: Mozilla should have adjusted to the fact that the first div now has a new height, and the second div should not cover up the first div. Testcase will follow. Marking as major, since it's critical to a project on http://www.strategyinformer.com/ This project involves fixing non-standard code on that site.
Reporter | ||
Comment 1•21 years ago
|
||
I will attach an example of correct rendering next.
Reporter | ||
Comment 2•21 years ago
|
||
Example of what I perceive to be correct rendering. The screenshot was obtained from IE (since it was the simplest way to make an example).
Comment 3•21 years ago
|
||
INVALID. IE treats height as min-height, which is wrong. Mozilla does it right.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•