d621899d50
This patch addresses a couple of smaller issues with the `PDFHistory` class: - Most, if not all, other viewer components can be reset in one way or another, and there's no good reason for the `PDFHistory` implementation to be different here. - Currently it's (technically) possible to keep adding entries to the browser history, via the `PDFHistory` instance, even after the document has been closed. That obviously makes no sense, and is caused by the lack of a `reset` method. - The internal `this._isPagesLoaded` property was never actually reset, which would lead to it being temporarily wrong when a new document was opened in the default viewer. |
||
---|---|---|
.. | ||
images | ||
README.md | ||
viewer.css | ||
viewer.html | ||
viewer.js |
Overview
Example to demonstrate PDF.js library usage with a viewer optimized for mobile usage.
Getting started
Build PDF.js using gulp dist-install
and run gulp server
to start a web server.
You can then work with the mobile viewer at
http://localhost:8888/examples/mobile-viewer/viewer.html.
Refer to viewer.js
for the source code of the mobile viewer.