View Single Post
Old 03-01-2023, 08:36 AM   #27
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by DrChiper View Post
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

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)
I can confirm that setting widows/orphans to 1, in <body>, does not work if the [Reading] options readingAdobeOrphans & readingAdobeWidows are not set in the Kobo config file. I'm going to guess that it stopped working at the same time the config options were introduced.

I don't have the tech skills to do a deep dive into the firmware code to confirm any of this but a plausible explanation of observations may be...

Whatever config values are set in readingAdobeOrphans & readingAdobeWidows will always override whatever values (if any) are present in <body>.

If readingAdobeOrphans & readingAdobeWidows are absent from config both default to a value of 2. In which case any widows/orphans values present in <body> will be overridden with a value of 2.

Any widows/orphans CSS hard-coded anywhere other than <body> should follow the normal rules of CSS inheritance and specificity.
jackie_w is offline   Reply With Quote