View Single Post
Old 08-21-2012, 03:33 AM   #8
Jellby
frumious Bandersnatch
Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.
 
Jellby's Avatar
 
Posts: 5,905
Karma: 4269879
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
Only the top margin, actually, and that's in accordance with the CSS spec (which says it may be ignored). That's at least with CSS2.1:

Quote:
Originally Posted by CSS2.1
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.
And despite what the note says, the situation in CSS3 does not change in the right direction:

Quote:
Originally Posted by CSS3
the computed values of the relevant 'margin-top' and 'margin-bottom' properties are set to '0'.
EDIT: Ah, the future spec may say something different:

Quote:
When an unforced page break occurs here, both the adjoining ‘margin-top’ and ‘margin-bottom’ are set to zero. [...] When a forced page break occurs at (1), the used values of any adjoining ‘margin-bottom’ are set to zero.
(emphasis mine, it says nothing about margin-top in forced page break, meaning it is retained.) But this is CSS3, which is not applicable even for ePub3, I'm afraid.

Last edited by Jellby; 08-21-2012 at 03:56 AM.
Jellby is offline   Reply With Quote