W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: [css3-page][css3-multicol] margins at page or column breaks

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 8 Jan 2009 23:43:42 +1300
Message-ID: <11e306600901080243q3e3283abn75dec16eb02fae28@mail.gmail.com>
To: "MURAKAMI Shinyu" <murakami@antenna.co.jp>
Cc: www-style@w3.org
On Thu, Jan 8, 2009 at 10:24 PM, MURAKAMI Shinyu <murakami@antenna.co.jp>wrote:

> 3. Margins at beginning of multi-column content will be set to zero?


I think the top-margin should not be set to zero. However, if the columns
element does not have a border then the top margin should collapse with the
bottom margin of the content before the columns and be placed above the
entire column set. Gecko implements this, because it's important for pages
that need to be rendered both by browsers with column support and those
without. Consider
<style>.section { column-width:30em; }</style>
<div class="section">
   <p>A
   <p>B
</div>
Having the top-margin of <p> rendered in the first column is very ugly.
Better to move it up outside the columns.

In your testcase, the columns element has a border, so that the top-margin
of its children cannot collapse out. I think it should be rendered in the
first column rather than lost.

3. Margins at beginning of multi-column content will be set to zero?
> Firefox=Yes
>

I think this is just a bug in our code.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
Received on Thursday, 8 January 2009 10:44:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:15 GMT