Quote:
Originally Posted by Turtle91
Not necessarily, Jon. As we've established many times, you can simply include fall-back coding for devices that aren't up to the current standards. If the device doesn't support a particular css then it is required to gracefully ignore it.
Jinx!!
As always, it depends on the capabilities of your device.
Good point on the html, body {height:100%}!
You can also use fall-back coding for those nasty older devices that don't support 90's technology... 
Code:
div[class^="v-"] {height:100%; width:100%; height:100vh; width:100vw;
display:table; position:fixed}
Decrepit devices will ignore the position:fixed & vh/vw if they are unsupported leaving you with:
Code:
div[class^="v-"] {height:100%; width:100%; height:100vh; width:100vw;
display:table; position:fixed}
IF, like the older ADE, it throws out the entire CSS if it encounters an unknown...then that is a broken system. Luckily, I won't code for such a system. IIRC ADE has fixed that. |
If you are coding for an eBook for sale, you have to code for such a system as that's what is used on a Kobo for ePub. There's no way you can make sure the eBook is read as KePub and not ePub on a Kobo. So you have to make sure the CSS is considered valid and that the eBook looks good enough.