View Single Post
Old 08-29-2014, 06:27 AM   #16
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
The problem appears to be your code. According to http://www.w3schools.com/cssref/pr_print_pageba.asp, the page-break-after property:

Quote:
Note: You cannot use this property on an empty <div> or on absolutely positioned elements
To test, I dropped it on my Glo (FW3.8.0) in various ways:
  • As a straight epub - it goes go to a new page.
  • With the name changed to *.kepub.epub - didn't go to another page
  • Converted to a kepub using calibre - it goes go to a new page. But,when I looked at the generated code, it actually split the file at this point. An epub-epub convert does the same thing. So this isn't a useful test.
  • Duplicated test_content.xhtml and put some text inside the two empty divs. This pushed the text to the next page.

From that, it looks like the kepub renderer is handling it more correctly than the epub renderer.
davidfor is offline   Reply With Quote