View Single Post
Old 04-25-2015, 01:01 AM   #936
cybmole
Wizard
cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.
 
Posts: 3,720
Karma: 1759970
Join Date: Sep 2010
Device: none
Quote:
Originally Posted by DiapDealer View Post
What do you mean? Almost all renderers will perform a page break if page-break-(before|after: always) is assigned to the class. Or did you mean something else?
well - testing needed - but where I have left this calibre code in a book at the end of each chapter , by your logic I should be seeing a new screen generated by the code followed by another new screen generated by start of next chapter. i.e. a double page turn at the end of every chapter. ditto if such code is left in at start of each html.
I don't see that, so unless renderers are smart enough to suppress that redundancy....

UPDATA: actual explanation, based on my sample of 1 books where I have not manually removed such code:
calibre defines the class as this
.mbppagebreak {
display: block;
margin: 0
}

so i'ts not going to do anything when applied in an empty div, except maybe cause a spurious line feed in some renderers

Last edited by cybmole; 04-25-2015 at 01:12 AM.
cybmole is offline   Reply With Quote