You can modify the
DEFAULT_URL variable in the
web/viewer.js file or you can append the
?file= query string to the viewer URL, e.g.
http://mozilla.github.com/pdf.js/web/viewer.html?file=compressed.tracemonkey-pldi-09.pdf. In the latter case, the PDF path/URL must be encoded using
The goal is to support all HTML5 compliant browsers, but since feature support varies per browser/version our support for all PDF features varies as well. If you want to support more browsers than Firefox you'll need to include compatibility.js which has polyfills for missing features. Find the list of features needed for PDF.js to properly work and browser tests for those features at Required Browser Features. In general, the support is below:
|Firefox Stable||yes||Windows and Linux|
|Chrome Stable||yes||Windows and Linux|
|Android||limited||none||Android's Web Browser version 4.0 or below lacks a number of features or has defects, e.g. in typed arrays or HTTP range requests|
|Safari||limited||none||Safari (desktop and mobile) lacks a number of features or has defects, e.g. in typed arrays or HTTP range requests|
|IE10+||limited||none||IE 10 or above may lack of features or may have defects.|
|IE9||limited||none||IE9 lacks a number of features and most notably typed arrays which causes subpar performance.|
|<=IE8||NO||none||IE8 and below are missing too many features to be supported.|
There is currently a Firefox, Chromium and Opera extension. The Firefox extension is well supported and actively worked on. The Chromium extension is maintained by a PDF.js contributor. The Opera extension can be found here. For installing the Firefox or Chromium extension, please refer to the readme.
First, you need to prepare your fork and setup the development environment. Don't forget to read the Contributing page. Second, make yourself familiar with the PDF format and PDF.js internals. Third, if you don't already have a certain issue you want to fix, choose one from the open issues labeled 5-good-beginner-bug. Last, submit a pull request for the review. During any part of the process we recommend to communicate with the PDF.js team on #pdfjs IRC channel at irc.mozilla.org if you have questions or need to find a reviewer.
PDF.js is mainly written for reading PDF files, not editing them. Because of that we don't yet support adding any kind of annotations. We do however support rendering a number of annotation types for viewing.
(warning, the following list may be incomplete)
The home, end, page up, page down and all arrow keys can be used to navigate the document.
User interface buttons or ctrl + mouse wheel can be used to change the zooming level, but keyboard shortcuts are also available:
(replace ctrl with meta on some configurations)
The only supported minifier as of now is Google Closure Compiler (see https://developers.google.com/closure/compiler). You can build a minified version of PDF.js using the following command:
CLOSURE_COMPILER="../path/to/closure/compiler.jar" node make minified
Yes. Please see http://mozilla.github.io/pdf.js/getting_started/ page for details. Also the code for the website at http://mozilla.github.io/pdf.js is located in the "gh-pages" branch. You can clone it using
git clone -b gh-pages https://github.com/mozilla/pdf.js.git pdfjs-gh-pages or download the archive.
There are also generic PDF.js library builds available at https://github.com/mozilla/pdfjs-dist. These builds can be installed via npm
npm install pdfjs-dist or bower
bower install pdfjs-dist.
Yes. The issues are used to track both bugs filed by users and specific work items for developers. Try to file one issue per problem observed.
Yes. PDF.js will attempt to recover usable PDF data (pages, content or fonts) and display the document. Please report the issue (see above) and we will take a look.
The best place is our firstname.lastname@example.org mailing list. You can subscribe to it using lists.mozilla.org or Google Groups. This way you will reach not only developers. As an alternative, you can join our weekly engineering meeting to discuss new ideas for the project.
The issue tracking system is designed to record a single technical problem. A bug report is something where a developer/contributor can work on. The GitHub issue tracker is not a good place for general, not well thought out or unworkable ideas. Most likely a discussion-type issue will not be addressed for a long time or closed as invalid.
We are glad to hear that and will try to help you, but first check examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare short well-documented example that demonstrate the problem and make it accessible online on your website, jsbin, etc. before opening a new issue or contacting us on the IRC channel -- keep in mind that just code snippets won't help us troubleshoot the problem. The issues that do not provide enough details will be closed as invalid/incomplete (see reporting issue above).
Please periodically check or subscribe to our email@example.com mailing list to be informed about changes in the PDF.js architecture/design or security announcements.
PDF.js is a general-purpose library to parse and render PDFs. At the moment it's included in the number of projects such as Firefox, Firefox OS, Chromium Extension, etc. We are recording our changes to the library with Github pull requests. Also the log of the changes is available from the git log.
The version number consists of three digits: the major release number, minor release number and build number. The major and minor number are selected when some major milestone is reached. The build number is incremented by one each time when new a commit is pushed to the master branch. For sanity check, we accompany each version number with the SHA number of the latest commit.
We are moving fast and trying to land as much good stuff as we can review and test. The generic viewer and development version of Firefox PDF Viewer extension always contain the latest PDF.js build and available for testing.
During cooldown period, about once or twice in 6 weeks, we push our library to the Firefox Nightly channel. We decided to tag/mark our master branch each time we do that, and at this point a beta release is created. To promote a latest beta to a stable release, we listen for feedback (via github, bugzilla, mailing list, or IRC) from the users and projects that use PDF.js library. If no critical issues (e.g. a build is unusable, majority of the documents cannot be rendered, etc.) appeared, we promote the build as stable. Otherwise we either discard the release by replacing it by new beta or redo the build with commits that will fix a critical issue.
Typically, PDFs with a smaller file size will be rendered faster and it depends on how big a single page is. The amount of pages does not affect the performance. It's essential that you optimize your documents for the web. See Optimize a PDF from Adobe's website for more information. There are more improvement techniques that we can suggest: