Sorry to have to disappoint you but the module simply wasn't maintained or mature enough to be acceptable.Channel 2012 wrote:Even though it isn't that good at rendering documents, it is still a big timesaver, and I'd hate to see it go.
The problem is not only that it would "not be as good at rendering documents" (which is an understatement), it also caused more than a few concerns about security -- PDF documents are significantly different from anything else the browser would handle, and throwing together a "viewer" in JavaScript can only get you so far; as well as a browser being an internet-connected application. PDF documents can be encoded many different ways and contain many different kinds of content all in a single package. Any one of those types of content can potentially be a hazard - if the viewer trips over something, it has the potential of having privileged pdf.js context becoming available to whatever content embedded in a PDF. Running content in privileged context is opening the door to remote code execution at browser privilege level on your system.
A plugin, however, would run in the restricted privilege plugin container, so even if it misbehaves there, it can't do much of anything (at most harmlessly crash). There's a good reason why plugins and the NPAPI are such good systems to use for non-native content.