View Single Post
Old 08-28-2014, 01:30 PM   #35
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: 7,561
Karma: 20150435
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
Quote:
Originally Posted by Psymon View Post
I was just thinking that if I made it before, then that bit of code -- as "empty" as it might be -- would invariably be inserted on the same page as the full-page image, and somehow screw that up.
Even if the dummy div would formally be in the page with the full-page image, in my tests at least it has not affected how things are displayed (but I don't think I've tried this particular test). If you find (or fear) that it does, you could indeed have two separate "pagebreak" classes, one for before and one for after.

But, on the other hand, the reason for having the dummy div is that you want to keep whatever top-margin you have defined, and not get it turned into 0. In your case you probably want 0 anyway, so maybe this is enough:

Code:
<!--Chapter Title Page-->
<div class="fullpage">
  <img ... />
</div>
<div class="pagebreak"/>
<!--Chapter Text-->
and you just add "page-break-before: always" to the div.fullpage style.
Jellby is offline   Reply With Quote