View Single Post
Old 03-26-2025, 02:11 AM   #6
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,355
Karma: 20171571
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by DNSB View Post
But what if your renderer is so borked that it does not ignore unsupported CSS?

Sorry but couldn't help myself. :
lol

Well, the current method (and reason we see 2 css files on many ePubs…thanks ADE) is to put the newer coding on a different style sheet…. If the device is so borked that it ignores the entire sheet then it still falls back to the older coding on the other sheet!

Users of those borked devices should get a refund for false advertising, as they are NOT meeting the ePub standard! Lol

To be fair to ADE they realized they screwed up and fixed that problem in their newer version… but they should update the software on those outdated, “borked”, devices.

Last edited by Turtle91; 03-26-2025 at 02:20 AM.
Turtle91 is offline   Reply With Quote