Thread: A bug in Sigil?
View Single Post
Old 07-15-2024, 12:40 PM   #8
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,777
Karma: 172313956
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by RbnJrg View Post
So far, I never had an issue for including a .js file in nav.xhtml. Sometime ago, I used both (in the same epub), the nav.xhtml an a xhtml toc, but as some ereaders had issues about not to show the nav.xhtml, I decided to do full visible the nav and not to include the toc. And as told you before, I didn't have any issue so far by including there a .js file (Readium and Webkit seem to handle that very well). Maybe this happens because the script doesn't change the structure of nav.xhtml; it only changes some .css styles.
That is quite possible. The sample shown in the item I read modified the structure of the human readable depending on the size of the screen so a large screen (iPad for instance) would show the pagelist while a smaller screen (Kobo Glo) would only show the ToC. I can't find the original article which was linked off Liz Castro's Pigs, Gourds and Wikis page quite a few years back though I did add to my 404 collection. Sheesh, it's only been 12 years...
DNSB is offline   Reply With Quote