Quote:
Originally Posted by jackie_w
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.
|
Great!
Quote:
Originally Posted by jackie_w
I'm going to guess that it stopped working at the same time the config options were introduced.
|
Prior this thread, I never heard about this option before. You have inside information? It is also very kobo specific, so you still have to include orphans/widows in the CSS when you use other ereader devices.
Quote:
Originally Posted by jackie_w
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. |
Seems a correct deduction. However, how did you determined the orphans/widows setting to become "2"? Is this somewhere mentioned?
So summarizing, Kobo CSS evaluation is (according to you):
- kobo hardcoded defaults,
- epub CSS settings,
- kobo config file settings.
in which each level is overriding the previous one.
And: the kobo config file settings only overrides the <body> orphans/widows settings.
Interesting
