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

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

From: Michael Day <mikeday@yeslogic.com>
Date: Sat, 10 Jan 2009 10:55:30 +1100
Message-ID: <4967E3F2.2040405@yeslogic.com>
To: "Grant, Melinda" <melinda.grant@hp.com>
CC: Håkon Wium Lie <howcome@opera.com>, "www-style@w3.org" <www-style@w3.org>

Hi Melinda,

>>  > 2. Margins at forced page breaks will be set to zero?
>> According to the spec, yes. (But I vaguely recall discussing 
>> this and reaching a different answer? Melinda? It could be 
>> argued that pages after forced page breaks should be treated 
>> like the first page.)
> Yes, we've struggled with this.  I don't think either answer fits all scenarios, so I think we'll need a control here, as XSL-FO has done.  We have pretty strong interop for 2.1, so I don't think we want to change this now.  (Arguments to the contrary, Michael?)

We currently respect vertical margins on the first page and after 
user-requested page breaks, eg. page-break-after: always, or use of 
named pages. This avoids the scenario of specifying a top margin on a 
chapter heading with absolutely no effect, which can be baffling.

Vertical margins at involuntary page breaks are set to zero.

Block margins are collapsed with page margins, assuming that the page 
has no border or margin content.

Best regards,


Print XML with Prince!
Received on Friday, 9 January 2009 23:56:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:23 UTC