View Single Post
Old 06-04-2012, 07:51 AM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 9,062
Karma: 40855212
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
It's a known bug with Kindle devices. It's even exhibited in the Kindle Previewer. The way to avoid it is to put your anchor point before/outside of the element you're trying to link to.

Consider this end-note link encountered in the text of a document:
Code:
<a href="#endnote1">[1]</a>
This anchor point (target) can exhibit the issue you're seeing:
Code:
<p id="endnote1" class="endnote">This is my first endnote.</p>
This is what you need to do to make sure it doesn't happen:
Code:
<a id="endnote1" /><p class="endnote">This is my first endnote.</p>
or:
Code:
<a id="endnote1"></a><p class="endnote">This is my first endnote.</p>
My example isn't exactly like your backlink, but the principle is the very same: put the anchor you're linking to before/outside of the element (p, h1, h2, h3, etc...) you're shooting for.

Last edited by DiapDealer; 06-04-2012 at 07:55 AM.
DiapDealer is offline   Reply With Quote