View Single Post
Old 01-04-2018, 12:31 AM   #110
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,891
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by tiltowait View Post
Ah, I should have made that clearer.

Anyway, here's another, semi-related problem. It's the same situation as before: one unbroken section of text being broken incorrectly. It differs in that it's unnecessarily breaking a small paragraph instead of valiantly not-breaking a large one.

This is a particularly weird instance, as there's obviously no reason for it to insert the page break. And before anyone asks: I did check the underlying HTML. The photographed text is enclosed in a single <p> tag of the same class as the rest of the body paragraphs. I can't see anything in the HTML or CSS that would cause it to behave this way. It's the second time I've seen something like this (the first was in a different book).
Was this paragraph the last in a chapter? Was it immediately followed by a </div> or </body> tag? I've seen a similar item where there was some funky blank line code after the last readable text in a paragraph.
DNSB is offline   Reply With Quote