Thread: A bug in Sigil?
View Single Post
Old 07-14-2024, 06:56 PM   #6
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: 46,960
Karma: 169810634
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
Yes, but the issue is that the property is erased when Sigil loads the epub. And Epubcheck allows the property "scripted" for nav.xhtml (in the .opf, property="nav scripted").
I'm not disagreeing that allowing the scripted property for the nav document is not prohibited. What I got from the article I read and made a couple of notes from is that the authors did not recommend using javascript in the nav document since it could cause issues with the renderer's ability to parse the file. Their suggested workaround was a vanilla navigation document that was hidden and a ToC file that could be fancified without needing to worry about the renderer parsing it.
DNSB is offline   Reply With Quote