Thanks Matt.
The base element makes the webviewer load go into an infinite loop of Javascript errors. I think I'll just cope with those assets being loaded via my app server for now.
Would it be possible to make these asset paths (the .html files) configurable in a later release, and ensure that all other assets including hand.png et al and the translation json files are loaded from the path passed into the PDFTron.Viewer constructor?
I've managed to back out all my patches to webviewer that I thought I needed, except for the change to WebViewer.js that allows me to pass an absolute html5Path and html5Mobile. I'm happy regenerating ReaderControl.html with new absolute paths -- I can do that with sed -- but would prefer to avoid maintaining a patch set against your Javascript code.
Regards
Donald