W3C home > Mailing lists > Public > www-style@w3.org > August 2010

Re: Retaining margins after pages and column breaks

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 02 Aug 2010 18:47:17 -0700
Message-ID: <4C577525.2010800@inkedblade.net>
To: David Hyatt <hyatt@apple.com>
CC: www-style list <www-style@w3.org>
On 06/09/2010 03:07 PM, David Hyatt wrote:
> What is the logic behind retaining margins after forced breaks being the
> default behavior in the CSS3 multi-column spec?  I would expect the
> opposite behavior to be the default.
>
> CSS2.1 says:
>
> http://www.w3.org/TR/CSS21/page.html#page-break-props
>
> "Note: It is expected that CSS3 will specify that the relevant 'margin-top'
>        applies (i.e., is not set to '0') after a forced page break."
>
> CSS3 Multi-Column says:
>
> http://www.w3.org/TR/2009/CR-css3-multicol-20091217/#column-breaks
>
> "However, the margin immediately after a forced page/column break will be preserved."
>
> It even goes on to include an example that explicitly reinforces this default.
>
> Can someone explain the logic behind this default, because I don't get it.
> We collapse away margins at the top of a document, i.e., on the first page...
> why would a header at the top of a later page be treated any differently?
> I have no objection to having control over the behavior, but shouldn't the
> default be that the margin-top is set to 0 after a forced break?

Why do you collapse the margin at the top of a document?

~fantasai
Received on Tuesday, 3 August 2010 01:48:06 GMT

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