[arspr]

Originally Posted by DNSB

Those may not have been orphans or widows -- I've found a quite a few ebooks that have lines such as <p>&nbsp;</p> to supply a nice wide space between paragraphs. Since the paragraph is only a single line, the widows/orphans setting has no effect on them.

I can assure they are orphans and widows, not single line paragraphs... Look at how the text is justified and how they don't have the ending period in orphans (which wouldn't happen in a single line paragraph), and how indentation is different and they start in lower-case in the widows (which wouldn't either happen in a single line paragraph).

Originally Posted by davidfor

Looks like Kobo have changed something with 3.0.0. For some time I have had the following in my kepub-book.css:

body {
	orphans: 0 !important;
	widows: 0 !important;
	}

And it worked perfectly. I just changed the numbers to 4, and it made no change. That suggests the ACCESS renderer is ignoring the widows and orphans CSS settings.

If you set 0 (or 1), it is like not working. So you wouldn't have probably noticed even if this feature was broken/un-implemented since long ago.

Nevertheless, and as you also say 2 should be the default value which should have filtered out lonely lines (but in the rare, very rare books which have this property set). My memory is not perfect and I was not looking for this effect, (probably because I was pretty used to it not working fine in my old Sony PRS-650, possible related to the weird rendering Adobe built-in renderer does in long paragraphs, when the weekday is Monday or when it's raining outside), but I'm nearly sure this feature has not worked since at least FW 2.8.1. I mean, I'm nearly sure I've never seen this feature working since I bought my Aura HD one month ago more or less.


EDITED ------

Because of some edits I've made to the book I'm currently reading (Las Legiones Malditas, which is the sideloaded kepubized epub in the previous screenshots), I can also say that neither page-break-inside: avoid;, nor page-break-after: avoid;, nor page-break-before: avoid; seem to work...