Closed
Bug 232924
Opened 22 years ago
Closed 19 years ago
{inc} Offset of rel. pos. child considered for rel. pos. parent height (overflow:hidden)
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: MatsPalmgren_bugz, Unassigned)
Details
(Keywords: regression, testcase)
Attachments
(2 files)
A relative positioned block with overflow:hidden takes the offset of a
relative positioned child into account when computing its auto height.
STEPS TO REPRODUCE:
1. load testcase
ACTUAL RESULTS:
The overflow:hidden box seems to take the child offset into account and
is bigger than the other two. Resizing the window fixes the problem.
EXPECTED RESULTS:
The green boxes should have the same height.
BUILDS & PLATFORMS TESTED:
Bug occurs in Mozilla nightly trunk build 2004-01-28-08 on Linux
Bug occurs in Mozilla 1.6 on Linux
Bug does NOT occur in Mozilla 1.5 on Linux
| Reporter | ||
Comment 1•22 years ago
|
||
| Reporter | ||
Comment 2•22 years ago
|
||
This is most likely the same problem (also fixed by resizing window).
Comment 3•22 years ago
|
||
This sounds like a block reflow issue, actually....
Component: Layout: R & A Pos → Layout: Block and Inline
QA Contact: core.layout.r-and-a-pos → core.layout.block-and-inline
Did this happen with 'overflow: -moz-scrollbars-none' in 1.5?
To answer my own question, it did, so this isn't really a regression.
Comment 6•21 years ago
|
||
worksforme
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041120
Comment 7•19 years ago
|
||
Both Testcases WFM using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061208 Minefield/3.0a1 ID:2006120804 [cairo]
| Reporter | ||
Comment 8•19 years ago
|
||
The bug occurs in Firefox 2004-12-05-07 on Linux,
it does not occur in Firefox 2005-09-18-06 (or later) on Linux.
The testcases are good candidates for the layout regression test suite, IMO.
-> WORKSFORME
Status: NEW → RESOLVED
Closed: 19 years ago
Flags: in-testsuite?
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•