[RbnJrg]

Originally Posted by Turtle91

edit: ooops...ninja'd by RbnJrg. I would completely trust his advice if you are using ePub2. But I think widows/orphans have been deprecated in ePub3, so you may need to check that if you are using ePub3.

Orphans and widows are honored under epub3. The main issue here are ereader devices. Under epub3, it is guaranteed that a break can be avoided after a <h>. Under epub2, with apps, practically there are no problems there and the code I posted will work, but with physical devices, things are not good. For example, with Kobo, things won't work (I don't know why Kobo is still using an old version of webkit). Fragmentation can be better avoided in a Nook or (it may seem paradoxical) in an old readers like Sony (both devices are based on RMSDK). And under epub2, is better to use:

.joined {
    display: inline-block;
    width: 100%;
}

than:

.joined {
    display: block;
    page-break-inside: avoid;
    break-inside: avoid;
}

The first code, will work everywhere, but with second code "page-break-inside: avoid" only willl work with RMSDK and "break-inside: avoid" only with readers that have one of the last versions of webkit (in Kobo for example, won't work).