Quote:
Originally Posted by JSWolf
What I am meaning is there is some code that does work for ePub 3 but for the older RMSDK that Kobo uses it's treated as an error and thus the entire CSS is ignored. That's what happens with Standard EBooks. They use some code that fails on a Kobo as ePub. That's why you have to make sure the code works well enough for that older version of RMSDK and doesn't cause RMSDK to think of it as an error and ignore the CSS.
|
Thus the comment that "the device does matter", but if the decrepit device completely ignores the entire css, then it is broken and does not conform to the spec. Kobo needs to fix it.
For the small(ish) percentage of people that publish specifically on the kobo, they should be aware of their broken product and bring it up with the manufacturer. If the manufacturer is unresponsive, and they continue using a broken product, then that is on them.
Quote:
Originally Posted by JSWolf
The other thing is, if the older ePub 2 type code does work such as % instead of vh, then there's no reason to use vh.
|
There is a reason to use vh: if you want to use the capabilities that vh provides, which % does not.
Quote:
Originally Posted by JSWolf
The other thing I'm not sure of is doesn't duplicate code lower down in the CSS get used instead of code higher up? If that is the case, then the % would be ignored for the vh and the code would not work in the older RMSDK.
|
The vh would get used, IF IT IS SUPPORTED. If it is not supported then, on spec compliant devices, it would ignore vh and use the % instead. (that's called fall-back coding)
Quote:
Originally Posted by JSWolf
But what do you do with ePub 3.x CSS that the older RMSDK thinks is an error and ignores the entire CSS? That would mean the code you are using is going to be an issue.
|
Upgrade your decrepit RMSDK device...
At some point you need to stop using the horse and buggy...
