18187 - [BLOCK] negative margin-bottom not working

Status: VERIFIED FIXED

(Core :: Layout, defect, P3)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

DESCRIPTION:  The negative margin-bottom in the test case to be attached
recently stopped working (see below).  The test case is simplified from the one
in bug 16548.

STEPS TO REPRODUCE:
 * load attached test case

ACTUAL RESULTS:
 * first paragraph comes before second paragraph - the spacing looks normal

EXPECTED RESULTS:
 * second paragraph should be above first

DOES NOT WORK CORRECTLY ON:
 * Linux, viewer, 1999-10-26-08-M11
 * Linux, apprunner, 1999-11-04-08-M11

WORKS CORRECTLY ON:
 * Linux, viewer, 1999-10-25-16-M11

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Attachment: test case described in bug

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I think this may be a dup of bug 18050, but that doesn't mention that it's a
regression and it's filed on Style System.

Comment 3

[leger]

Updating to default Layout Assignee...kipp no longer with us :-(

Comment 4

[troy]

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.

Comment 5

[buster]

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.

Comment 6

[Hixie (not reading bugmail)]

Slightly increasing the detail on the summary. David: If I misunderstood the
bug, feel free to flame me and I'll change it back. ;-)

Comment 7

[Hixie (not reading bugmail)]

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...

Comment 8

[ekrock's old account (dead)]

Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!

Comment 9

[buster]

mine! mine mine mine!  all mine!  whoo-hoo!

Comment 10

[rickg]

moving all buster m15 bugs to m16.

Comment 11

[buster]

Important to get this right, but won't make beta2.  Moving to M18.

Comment 12

[buster]

redistributing bugs across future milestones, sorry for the spam

Comment 13

[buster]

This bug has been marked "future" because the original netscape engineer working 
on this is over-burdened. If you feel this is an error, that you or another 
known resource will be working on this bug,or if it blocks your work in some way 
-- please attach your concern to the bug for reconsideration. 

Comment 14

[Hixie (not reading bugmail)]

Nominating for nsbeta2 to bring this to the attention of the PDT. This is a 
CSS1 compliance issue. We are currently buggy.

Comment 15

[Hixie (not reading bugmail)]

Since this is not a top100 bug (and because David suggested it) I am moving this
from nsbeta2 nomination to nsbeta3 nomination. Since this actually works in IE5,
to some extent, as well as being buggy CSS1 behaviour, I believe this should be 
an nsbeta3 blocker.

Comment 16

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Stealing and...

Comment 17

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

...marking fixed.  Same problem as bug 18050.

Comment 18

[bsharma]

Verified.
Windows: 2000-07-13-09-M17
Linux:   2000-07-13-08-M17]