This is a long standing issue with kindle firmware. Basically, under some circumstances parts of the text fail to render and you have to go back a page and forward again to work around it.
IIRC this usually happens when an anchor (the destination for a link) is close to/spans an internal text boundary in the MOBI/AZW3 file. MOBI files have the text/markup split up internally into fixed size chunks and the Kindle renderer basically renders one chunk at a time. THere can be issues if yo follow a link/TOC entry that goes to alocation close to the boundary of one of those chunks.
I dont think it is anything in the HTML markup itself that causes this -- however there is no way to be sure of that since we cant see the source code of the kindle renderer
|