Closed Bug 787310 Opened 12 years ago Closed 12 years ago

<ul> with moz-column-count does not account for margin-top on <li>s

Categories

(Core :: Layout, defect)

17 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: kyle.kalstabakken, Unassigned)

Details

(Keywords: testcase)

Attachments

(1 file)

Attached file Test case
Create a <ul> with moz-column-count:3
Create six <li> (with content) and margin-top:20px

Actual Result:
First <li>s in columns 2 and 3 have no top margin, causing the first column to look offset

Expected Result:
All <li>s have a top margin of 20px

Example html is attached.
Attachment #657146 - Attachment mime type: text/plain → text/html
It's a recent regression in Firefox 17.

m-c
good=2012-07-20
bad=2012-07-21
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3a05d298599e&tochange=446b788ab99d

Suspected bug:
Mats Palmgren — Bug 616722 - Make ColumnSetFrame a block margin root. Make the first column a margin root at the top edge, and the last column at the bottom. r=roc
Blocks: 616722
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression, testcase
Version: 18 Branch → 17 Branch
OS: Linux → All
Hardware: x86_64 → All
This is an intentional change.  The tests in bug 616722 covers this case.
No longer blocks: 616722
Status: NEW → RESOLVED
Closed: 12 years ago
Keywords: regression
Resolution: --- → INVALID
Could you please explain why this behavior is desired? For me at least it is completely unexpected and unintuitive, so I would like to understand the rationale behind it.
Sure, the rationale is that margins at column breaks should behave the
same as at page breaks, i.e. margins are suppressed at the top of
a column/page break, except if it's a forced break, then the margins
should appear.  That's what Elika (who writes the spec[1]) told me
when I asked her about it, IIRC.

[1] http://www.w3.org/TR/css3-break/
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: