- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Wed, 20 Jun 2012 14:42:08 -0700
- To: www-style@w3.org
On 06/20/2012 04:38 AM, Simon Sapin wrote: > Hi, > > The current css3-page ED says: > >> In the normal flow, page breaks may occur at the following places: >> >> In the vertical margin between sibling block boxes (or rows in a >> table). When an unforced page break occurs here, both the adjoining >> ‘margin-top’ and ‘margin-bottom’ are set to zero. > > > On the same subject, CSS 2.1 says: > >> In the normal flow, page breaks can occur at the following places: >> >> In the vertical margin between block-level boxes. When an unforced >> page break occurs here, the used values of the relevant 'margin-top' >> and 'margin-bottom' properties are set to '0'. When a forced page >> break occurs here, the used value of the relevant 'margin-bottom' >> property is set to '0'; the relevant 'margin-top' used value may >> either be set to '0' or retained. > > Which is correct? Apparently this was changed in 2.1 in the process of making it a REC, but the change was not ported to > css3-page css3-page specifies the correct behavior. Both options were allowed in CSS2, but for level 3 a forced break causes the subsequent margin-top to appear. Note that margins are truncated at the bottom of the page in all cases. ~fantasai
Received on Wednesday, 20 June 2012 21:42:36 UTC