[Tex2002ans]

Originally Posted by odamizu

But at least I got rid of the widows/orphans validation error

Originally Posted by yekim54

Same here. I've been using the advice in the following post the past 9+ years

Well wipe that 0 and make it a 1.

0 is invalid, always has been:

CSS specs (widows and orphans):

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.

Originally Posted by odamizu

What I meant was, I use them for my own purposes, but it always throws a validation error, which I ignore.

What throws a validation error?

epubcheck? Calibre's check? Or something else?

Originally Posted by odamizu

Then the "invalid" css succeeds in making my ereaders do what I want them to.

When CSS runs against a property it doesn't understand, it's designed to completely ignore that part. (For example, if a CSS2 reader runs across CSS3, it will also have no idea what those properties mean... but it will render the parts it does understand.) So proprietary entries like adobe-hyphenate shouldn't hurt one bit.

But, there are a few CSS implementation bugs to note:

• RMSDK doesn't like actual invalid code. (Missing ; or missing a {}.)
  • It chucks away THE ENTIRE CSS file.
• Other devices have issues with Media Queries.
  • Example, there was bugs on Nooks where everything after a Media Query (even if valid) got ignored.
  • Key is to move them to the very end, or in their own separate CSS file: https://github.com/dvschultz/99problems/issues/22