Quote:
Originally Posted by graycyn
Thanks, good to know! I'll probably just use the non-webkit one then.
I get paranoid, I've seen too many weird things happen, where all is fine, and then an ebook hits ONE app, where suddenly, things are not as I expect.
Just this morning, I popped a book into the Google Books app ... only to find that some headings weren't centered. Yet, the heading tags all had:
Code:
text-align: center;
text-indent: 0;
but did contain spans. Which, every place else I'd tested, were inheriting the text-align and text-indent properties as per normal. But not for Google Books. Adding the code to the span classes as well fixed it, though shouldn't have been necessary?
I don't recall having had that problem in the past in that app, actually, so maybe something changed there since I last made a book. It all makes my brain hurt!
But I suppose it also all keeps my brain from rotting with disuse, LOL! |
It doesn't matter if the program is webkit based or not. The thing that matters is never use webkit code as it's not valid ePub code.