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

Retaining margins after pages and column breaks

From: David Hyatt <hyatt@apple.com>
Date: Wed, 09 Jun 2010 17:07:08 -0500
Message-id: <2A9DB92B-9D71-4087-8E56-9A74B40C73BF@apple.com>
To: www-style list <www-style@w3.org>
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:


"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:


"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?

Received on Wednesday, 9 June 2010 22:07:42 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:13:47 UTC