View Single Post
Old 03-01-2018, 08:54 AM   #19
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,101
Karma: 92190113
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by Tex2002ans View Post
For Kindles, I bet Amazon has their own custom renderer, but the rules Apple set for iOS forces them to use Webkit just like the other browsers (Firefox, etc. etc.). This is probably why Kindle iOS is the bastard step-child.
I also believe that this is the most likely reason. The KF8 renderer appears to be a customized version of WebKit. It is likely that Apple would not allow it to be used in the iOS app.

Instead of KF8, Kindle for iOS uses the same content as used by Kindle Cloud Reader, which is Amazon's web app. The K4iOS app includes the KCR JavaScript and it runs that using the iOS native browser engine.

The newer KFX format avoids this issue because it is not based on HTML.

Last edited by jhowell; 03-01-2018 at 08:57 AM.
jhowell is offline   Reply With Quote