Closed
Bug 18206
Opened 25 years ago
Closed 22 years ago
[MARGIN-C]top margin on first flow child lost after out-of-flow child
Categories
(Core :: Layout, defect, P2)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla1.3alpha
People
(Reporter: dbaron, Assigned: dbaron)
References
Details
(Keywords: css1, testcase, Whiteboard: [Hixie-P2][CSS1-5.5.1][patch])
Attachments
(2 files)
DESCRIPTION: When the children of the body element begin with (1) an absolutely
positioned element followed by (2) a non-positioned element, then the top margin
of (2) is ignored.
STEPS TO REPRODUCE:
* load attached test case
ACTUAL RESULTS:
* the red DIV saying it has a 400px top margin is at the top of the page
EXPECTED RESULTS:
* it should be 400px (+ a few extra) from the top.
DOES NOT WORK CORRECTLY ON:
* Linux, apprunner, 1999-11-04-08-M11
* Linux, viewer, 1999-11-04-08-M11
ADDITIONAL INFORMATION:
The test case is similar to that in bug 16893.
|
Assignee | |
Comment 1•25 years ago
|
||
Why are you re-reassing layout bugs? Do NOT touch layout bugs.
The bugs are assigned to Kipp so they can stay neatly organized until we have a
new owner for the block/inline code.
mass moving all Kipp's pre-beta bugs to M15. Nisheeth and I will
prioritize these and selectively move high-priority bugs into M13 and M14.
Summary: margin ignored after absolutely positioned element → [FLOAT] margin ignored after absolutely positioned element
|
||
Updated•25 years ago
|
Summary: [FLOAT] margin ignored after absolutely positioned element → [FLOAT] {css1} margin ignored after absolutely positioned element
|
|
||
Comment 6•25 years ago
|
||
Migrating from {css1} to css1 keyword. The {css1}, {css2}, {css3} and {css-moz}
radars should now be considered deprecated in favour of keywords.
I am *really* sorry about the spam...
|
||
Updated•25 years ago
|
Summary: [FLOAT] {css1} margin ignored after absolutely positioned element → [FLOAT] margin ignored after absolutely positioned element
M17, P2.
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: M16 → M17
|
|
Assignee | |
Updated•24 years ago
|
Summary: [FLOAT] margin ignored after absolutely positioned element → [BLOCK][ABSPOS] margin ignored after absolutely positioned element
|
||
Comment 10•24 years ago
|
||
win32 2000071308
|
||
Comment 11•24 years ago
|
||
Putting on [nsbeta2-] radar. Not critical to beta2.
Whiteboard: [nsbeta2-]
|
|
Assignee | |
Comment 12•24 years ago
|
||
Assigning to myself to investigate.
Assignee: buster → dbaron
Status: ASSIGNED → NEW
Summary: [BLOCK][ABSPOS] margin ignored after absolutely positioned element → [MARGIN-C][ABSPOS] margin ignored after absolutely positioned element
|
|
Assignee | |
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M17 → M18
|
||
Comment 14•24 years ago
|
||
post a patch for review?
|
|
Assignee | |
Comment 15•24 years ago
|
||
Fix undone due to other issues...
Whiteboard: [fix in hand][nsbeta2-] → [nsbeta2-]
|
|
Assignee | |
Comment 16•24 years ago
|
||
Giving margin collapsing bugs that I have not fixed to buster.
Assignee: dbaron → buster
Status: ASSIGNED → NEW
Target Milestone: M18 → ---
|
|
||
Comment 17•24 years ago
|
||
needs investigation. David, it would help if you could briefly describe what
you attempted to fix this bug, and what problems you ran into. Thanks.
|
|
Assignee | |
Comment 18•24 years ago
|
||
The code to fix it is #if 0 within the patch I attached to bug 50959.
The issues are described in
http://lists.w3.org/Archives/Member/w3c-css-wg/2000JulSep/0129.html .
Keywords: correctness
|
|
Assignee | |
Comment 19•24 years ago
|
||
|
|
Assignee | |
Updated•24 years ago
|
Summary: [MARGIN-C][ABSPOS] margin ignored after absolutely positioned element → [MARGIN-C]top margin ignored on first nor-flow child when not first child
|
|
||
Comment 20•24 years ago
|
||
P2 bugs will not make RTM. Milestone -> Future.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
|
|
||
Comment 21•24 years ago
|
||
*** Bug 56233 has been marked as a duplicate of this bug. ***
|
|
||
Comment 22•24 years ago
|
||
From bug 56233:
STEPS TO REPRODUCE
http://www.webstandards.org/css/winie/box_vert.html
There is a <P> with a margin-top after a float. The margin is ignored.
Reflows don't help.
RESULTS
For that test case, there should be 40px of white at the top of the page.
Currently we skip the white and go straight to silver.
christine, Could you add this test case to your list of CSS tests? I'm not quite
sure how we missed it, but I couldn't find it on either of our CSS test case
lists... someone pointed this out to me on IRC! :-/
Keywords: testcase
QA Contact: petersen → chrisd
Summary: [MARGIN-C]top margin ignored on first nor-flow child when not first child → top margin on first flow child lost after out-of-flow child [MARGIN-V] [FLOAT]
|
|
Assignee | |
Comment 23•24 years ago
|
||
Undoing Ian's mangling of radars. :-) It's MARGIN-C, not MARGIN-V, and this has
no more to do with floats than with any other way of taking things out of the
flow, such as absolute positioning. And I was wondering why I couldn't find
this bug with a MARGIN-C search...
Summary: top margin on first flow child lost after out-of-flow child [MARGIN-V] [FLOAT] → [MARGIN-C]top margin on first flow child lost after out-of-flow child
|
|
Assignee | |
Comment 24•24 years ago
|
||
*** Bug 60195 has been marked as a duplicate of this bug. ***
|
||
Comment 25•24 years ago
|
||
Note from dupe 60195:
top-margin is only lost if the parent element has border:none and padding:0.
|
|
||
Comment 26•24 years ago
|
||
Netscape's standard compliance QA team reorganised itself once again, so taking
remaining non-tables style bugs. Sorry about the spam. I tried to get this done
directly at the database level, but apparently that is "not easy because of the
shadow db", "plus it screws up the audit trail", so no can do...
QA Contact: chrisd → ian
|
|
||
Comment 27•23 years ago
|
||
*** Bug 72060 has been marked as a duplicate of this bug. ***
|
|
||
Updated•23 years ago
|
Whiteboard: [nsbeta2-] → [Hixie-P2]
|
||
Comment 28•23 years ago
|
||
Build reassigning Buster's bugs to Marc.
Assignee: buster → attinasi
Status: ASSIGNED → NEW
|
||
Comment 29•22 years ago
|
||
The bug does not seem to occur in quirks mode.
The output of the code below differs only as
long as the doctype is specified.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/strict.dtd">
<html><body>
<p>test</p>
</body><html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/strict.dtd">
<html><body>
<div style="position: absolute; left: 0px; top: 0px;"></div>
<p>test</p>
</body><html>
|
||
Updated•22 years ago
|
Whiteboard: [Hixie-P2] → [Hixie-P2][CSS1-5.5.1]
|
|
Assignee | |
Comment 30•22 years ago
|
||
This is fixed by my patch on bug 44242. It was also mentioned on
c.i.w.a.stylesheets this weekend (Problem with "margin-top" in Mozilla). Taking
bug, Target=1.3alpha.
Assignee: attinasi → dbaron
Depends on: 44242
Whiteboard: [Hixie-P2][CSS1-5.5.1] → [Hixie-P2][CSS1-5.5.1][patch]
Target Milestone: Future → mozilla1.3alpha
|
|
Assignee | |
Comment 31•22 years ago
|
||
*** Bug 74557 has been marked as a duplicate of this bug. ***
|
|
Assignee | |
Comment 32•22 years ago
|
||
Fix to bug 44242 checked in to trunk, 2002-11-28 11:29 PST.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
|
||
Comment 33•22 years ago
|
||
*** Bug 184067 has been marked as a duplicate of this bug. ***
|
||
Comment 34•22 years ago
|
||
The margin-top of div.two disappears when div.one has position fixed.
Didn't test in the latest build because I don't want to. Anyone else?
You need to log in
before you can comment on or make changes to this bug.
Description
•