Quote:
Originally Posted by Hitch
Yes, to those of us who stare at them, they're offensive, but...largely, they're also harmless.
|
Early days, yet, in my investigations, but I think I've noticed a detrimental effect with Android reading apps with regard to the extraneous spans. I recently bought a commercial book that contained all the extra spans that displayed oddly on the Kindle Fire and Kindle for Android apps. In essence, the margin-top property of a specific paragraph class was being ignored (regardless of where in the "page" or file it occurred). I didn't notice the issue with the same book in Kindle for Windows or on a newer eink Kindle. Stripping the "naked" spans seemed to remedy the problem. The same effect was experienced with the commercial epub of the same title when viewed with the Android Kobo app, but I didn't experiment any further in that regard.
It's possible I've missed something obvious, but so far, I'm left with notion that "over spanning" just might create rendering problems on the Kindle For Android platform (and maybe Kobo).
I know for a fact that it affects Bookari's proprietary cloud sync feature. With all the spans in place, the best Bookari can do with regard to syncing reading progress (at least with epub3) is to open at the beginning of the most recent chapter. Without them, their cloud-sync performs rather admirably.
All "for what it's worth," natch.
