Quote:
Originally Posted by Moonbase59
The modified EPUB and CSS are in the attached ZIP for you to study. This version works nicely (and behaves the same) on all readers noted above. I also include actual screenshots from a Pocketbook Era, and from Foliate.
I don’t have any Pocketbook Apps here, but if they use the same (or at least a compliant) renderer in those apps, it should display the same. I’m not sure about iOS, Apple probably forces everyone to use their WebKit engine (from Safari), so for more special features you might have to use the -webkit-prefixes in addition there. Try to use as few as possible. Vendor-specific is evil. Like you say, we’ve had that with IE, back in the days.
|
Yeah, what I thought, unfortunately it seems to be a bug in the iOS app. All other reader work fine, and since you can confirm that your kind of PocketBook works as well, it is an application issue. Can't say whether Android is affected too, but I will find out the next days.
Quote:
Originally Posted by Moonbase59
All behave the same (and rightly so), because your CSS in styles.css is at fault, not any of the readers.
Hint: Try to start out with easy CSS, don’t overcomplicate it.
|
If you mean ".p1.p1" that's perfectly fine CSS, it's somewhat called raising precedence by connecting a class to itself and often used to avoid "!important". You could even do "p.p1.p1" and get a further level up. It's not a CSS functionality per definition, but also not faulty. I've never encountered a browser which didn't honor it, but maybe that is different with ebook readers. However, this was a last ressort after none of the previous attempts succeeded.
I've written CSS for over 20 years and am still willing to learn more, although there is a reason I mostly developed backend: predictability
Thank you and wish you a nice sunday