MobileRead Forums - View Single Post

KevinH · 08-08-2023, 07:10 PM

Not a bug but expected behaviour. XHTML comments are not part of the parsed DOM tree. They are stripped out during parsing by the Chrome/Blink engine used by Preview so there is nothing in Preview to navigate to and visa-versa.

The correct way to indicate page numbers is with either an empty span with id to the upcoming page, or with the span wrapping the first word of a page with an id to that page. Not with xhtml comments. These in turn can be used to build actual page list links for the ncx or nav. I have seen people use "a" tags as well with no contents, just an id to act as the link destination.

And the best way to exactly sync Preview's location to CodeView and the reverse is to click on visible text shared by both.

08-08-2023, 07:10 PM	#2
KevinH Sigil Developer Posts: 8,809 Karma: 6000000 Join Date: Nov 2009 Device: many	Not a bug but expected behaviour. XHTML comments are not part of the parsed DOM tree. They are stripped out during parsing by the Chrome/Blink engine used by Preview so there is nothing in Preview to navigate to and visa-versa. The correct way to indicate page numbers is with either an empty span with id to the upcoming page, or with the span wrapping the first word of a page with an id to that page. Not with xhtml comments. These in turn can be used to build actual page list links for the ncx or nav. I have seen people use "a" tags as well with no contents, just an id to act as the link destination. And the best way to exactly sync Preview's location to CodeView and the reverse is to click on visible text shared by both. Last edited by KevinH; 08-08-2023 at 07:31 PM.