Dan Rosen Reporter
	Description • 25 years ago

I'm not absolutely certain about this, but the first-child pseudo-class may be
broken, as described in the attached URL (testcase). Reasoning is described at
that URL.

The only other option, if my theory is invalid, is that list-item numbers are
themselves misaligned.

	David Baron :dbaron:
	Comment 1 • 25 years ago

There's no value 'normal' for margin-top.

Furthermore, the only way to reduce the space between the first list item and
the paragraph above it is to reduce the bottom margin on the p (out of the
list), the top margin on the ol, and the top margin on the p (in the list).
This is because of collapsing margins.

However, the list-item misalignment *may* be a bug, but has absolutely nothing
to do with :first-child.  It probably has something to do with line-height.  I
have to check the rules on aligning list markers...

This should probably go to Layout.

	David Baron :dbaron:
	Comment 2 • 25 years ago

The CSS section on markers (which I've recommended that you follow for things
with display: list-item so you'll be forwards-compatible) is not very clear on
this point.  I tend to think the marker *should* be properly aligned, though.

Simplified testcase to be attached.

	Pierre Saslawsky
	Comment 4 • 25 years ago

Changing the title to "List markers are not properly aligned" from "{css2} first-
child broken". Reassigned to Troy.

	troy
	Comment 6 • 25 years ago

Block related so re-assigning to Kipp's bug list

	buster
	Comment 7 • 25 years ago

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.

	Hixie (not reading bugmail)
	Comment 8 • 25 years ago

Yes, the marker box should be aligned with the text in the list-item box, even
if the list-item has line-height:2, because both the marker and the text in the
list-item box have vertical-align:baseline and both participate in the same
calculations for sizing the line-box, so both are aligned to the same baseline.

David: This might be relevant for your "David's Inline Box Model" document.

	Hixie (not reading bugmail)
	Comment 9 • 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...

	buster
	Comment 10 • 25 years ago

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

	Matthew Brealey
	Comment 11 • 25 years ago

Original URL is 404

	Hixie (not reading bugmail)
	Comment 12 • 25 years ago

Disregard the comments from "webmaster@richinstyle.com", the original URL is
actually not 404 at all. In addition, the two attachements are very similar to
the original test case anyhow.

	rickg
	Comment 13 • 25 years ago

moving all buster m15 bugs to m16.

	buster
	Comment 14 • 24 years ago

redistributing bugs across future milestones, sorry for the spam

	Hixie (not reading bugmail)
	Comment 15 • 24 years ago

*** Bug 47190 has been marked as a duplicate of this bug. ***

	Hixie (not reading bugmail)
	Comment 16 • 24 years ago

Nominating for nsbeta3. This is a standards compliance issue, and IE5.5 gets it
right so it would look very bad for us to get it wrong.

	Marc Attinasi Assignee
	Comment 17 • 24 years ago

Denying approval for beta3: too many bugs and not enough resources, so this one 
will have to be atteneded to in the future.

	Hixie (not reading bugmail)
	Comment 18 • 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...

	Dan Rosen
	Comment 19 • 24 years ago

Just pinging this bug... Ian, do we still need more thorough testcases? It'd be
nice to have this fixed.

	Hixie (not reading bugmail)
	Comment 20 • 24 years ago

dr: We always need more thorough testcases, but in this case they are not needed
in order to fix this bug.

To fix this bug we need to make sure that the marker box (also known as the
::list-item-marker if we use unpublished CSS3 terminology) takes part in the
vertical alignment and sizing of the first line box of the element which has
display: list-item. Should that element be empty, a line box should be created
immediately inside said element (as if ::before had been set to content:'').

	Dan Rosen
	Comment 21 • 24 years ago

whoa. i don't speak formatting :) removing cc.

	Kevin McCluskey (gone)
	Comment 22 • 23 years ago

Build reassigning Buster's bugs to Marc.

	Boris Zbarsky [:bzbarsky]
	Comment 23 • 21 years ago

So... is this still a problem?  I don't see any alignment problems on the
testcases.....

	Mats Palmgren (inactive)
	Comment 24 • 21 years ago

WFM, 2003-10-31-05 trunk Linux

	Boris Zbarsky [:bzbarsky]
	Comment 25 • 21 years ago

OK, marking so (since it worksforme too).