View Single Post
Old 07-17-2014, 01:00 PM   #179
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 48,029
Karma: 174315100
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
If 0 and 1 both work the same, then I see no harm using either value.
The harm can come in the future when your standards compliant ereader sees the value of 0 for widows or orphans and ignores it.

The CSS Level 3 Fragmentation module states the following (which I've quoted once before):

Only positive integers are allowed as values of ‘orphans’ and ‘widows’. Negative values and zero are invalid and must cause the declaration to be ignored.

Please note the section that I have bolded. And yes, testing with a ePub3/CSS 3 compliant application, setting widows and orphans to 0 gave the same effect as no widows and orphans declarations, i.e. the default of 2 was applied.

Regards,
David
DNSB is offline   Reply With Quote