View Single Post
Old 03-01-2023, 04:53 AM   #22
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 1,030
Karma: 2003162
Join Date: Jun 2011
Device: PC, t1, t2, t3, Clara BW, Clara HD, Libra 2, Libra Color, Nxtpaper 11
Quote:
Originally Posted by jackie_w View Post
This is news to me, also! Can I confirm that you're just talking about widows/orphans with this statement? Or is it any CSS property in <body>?
Yes, I'm just referring to orphans/widows. That said, I wouldn't be surprised that other inheritance issues may exist, but I have yet to encounter them.

Originally, I just used the earlier by others above stated <body> definition:
Code:
body {
  . . .
  orphans: 1;
  widows: 1;
  . . .
}
and assumed they worked in <p>, <div>, etc. and never checked further.
About a month ago, I had a text with mixed paragraphs comprising multiple lines and noticed they behaved funny at the kobo bottom page boundaries. That is, a paragraph sometimes was completely moved to the next page, leaving a kind of huge gap at the bottom of the current displayed page. This is odd, as the orphans/widows setting indicates at least 1 line of the next paragraph must be placed on the current page. I tried several things, dived again in the CSS documentation, but could not find a solution.
Reasoning did suggest that the orphans/widows settings were not inherited by the paragraph <p> (and <div>), which I could not really believe. But hey, paper specs are not always (correctly) translated into code I knew from past experiences. So I did hard coded my CSS <p> & <div> settings to include orphans/widows to check this. And then it worked perfectly. QED

Well, for me that is. Some rumors in this thread still doubt this

So I suggest to try it yourself and see whether it works for you as YMMV. It might be that my kobo's are mondaymorning devices (latest FW)

Let us know so we may learn.
DrChiper is offline   Reply With Quote