Quote:
Originally Posted by Jellby
Then I'm sorry but the W3C CSS validator is wrong (for our purpose at least). As said before, the CSS spec says that unknown properties should simply be ignored. There should be an option to treat non-existing properties as warnings.
A different thing would be, for instance, if you had "visibility: none". "visibility" is a known property, but "none" is not an allowed value for it, so that's clearly an error.
|
Thank you and thank you everyone! I feel better about including adobe-hyphenate now! Before, I just felt completely unsure, since it was an error message rather than a warning.
The Android apps I ran the book through (in case anyone is interested) were:
Aldiko, Bluefire, Bookari, Cool Reader, FBReader, Gitden Reader, Google Play Books, Kobo, Lithium, Moon+ Reader, Nook, Overdrive, Pocketbook and UBReader.
Some supported the CSS better than others, but the book was readable in all with or without adobe-hyphenate included.
Sent from my Nexus 9 using Tapatalk