|
It sounds like some of the Android based e-readers are very broken.
Navigating an internal link using "#" from any html document to the top of that page has been a part of the html spec since before even html4. All e-readers should support a spec that old by now.
An e-reader can have many navigation menus generated.
For example on epub2:
1. a generated toc from the ncx (no internal linking from ncx to itself is allowed or needed) The ncx is machine parseable.
2. a navigation aid based on the opf guide to major sections of the book
(again no internal linking within the guide to itself is allowed or needed)
3. An separate html file created to act as a user viewable table of contents
(here internal linking is possible) typically added to the opf spine. Typically is not machine parseable easily.
Under epub3 you have the toc and landmarks sections both from the nav.xhtml used to replace the ncx and the opf guide. But because the nav.xhtml is html5 based, internal links from the nav to itself are possible under the spec. Although pure html5, the nav.xhtml must always be machine parseable. It need not be added to the spine or may be added as linear = no.
In older epub2 only e-readers, adding an ncx and opf guide section to an epub3 helps to make them more usable.
So in any and all html based table of contents, using a "#" to navigate internally to within itself to the top of page must work or your e-reader app is very broken as that has long been part of the html and html5 specification.
|