Quote:
Originally Posted by DNSB
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.
|
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.