React PDF viewer VS PDF.js

Ref: https://react-pdf-viewer.dev/

I have a GQL mutation that updates the data for an event, I want to request an update when a .pdf document is loaded. For loading PDFs I'm using React PDF Viewer the package provides an event called onDocumentLoad which gets called when a .pdf file is successfully loaded.

React PDF Viewer

I have a small modal window that displays the contents of a .pdf file, I am using React PDF Viewer for this.

What is the great selling point compare to use the native PDF view builtin to all modern browsers?

I really hate it when websites tries to be smart about PDF viewing. The builtin view is much better and faster.

The demo at https://react-pdf-viewer.dev is just not as good as opening the PDF directly in the browser.

I am using a React PDF viewer in my project. I have a react mui dialog component that I use with react draggable to drag it around.

I first started building the app in the browser, using PDF.js and Download.js to take a PDF and edit it, and then download it to your computer.

pdf2json is a module that transforms PDF files from binary to JSON format, using pdf.js for its core functionality. It also incorporates support for interactive form elements, enhancing its utility in processing and interpreting PDF content.

Why not PDF.js?

I'd think opening a PDF in your browser would be at the same risk-level you associate with going to any random URL. On Firefox at least, I'm pretty sure the built-in PDF viewer is simply JS parsing and rendering the PDF anyway -- nothing with elevated permissions:

https://mozilla.github.io/pdf.js/

The PDF features are actually an extension, just one built in as Firefox's default pdf viewer.

It's called pdf.js https://github.com/mozilla/pdf.js/

You can actually use this pdf viewer in another browser like Chrome if you'd like, there's a demo URL on there.

We use Mozilla's PDF.js via the pdfjs-dist NPM module to load pages from a PDF file. The loadPdfPages function reads the PDF file and extracts its content. It returns an array where each object contains the page number and the text of that page.

The problem is that there simply wasn't a better option at the time.

Ogg Vorbis was a novelty at best, and it was the only decently widely adopted open source competitor for any of the items listed that was available at the time.

HTML5 was only just published when Chrome launched. So Flash was at that point the only option available to show a video in the browser (sure, downloading a RealPlayer file was always an option, but it was clunky, creators didn't like people being able to save stuff locally, and was also not open source). Chrome in fact arguably accelerated the process of getting web video open sourced: Google bought On2 in 2010 to get the rights to VP8 (the only decent H.264 competitor available at that point) so they could immediately open source it. The plan was in fact to remove H.264 from Chrome entirely once VP8/VP9 adoption ramped up[1], but that didn’t end up happening.

Flash was integrated into Chrome because people were going to use it anyway, and having Google distribute it at least let them both sandbox it and roll out automatic updates (a massive vector for malware at the time was ads pretending to be Flash updates, which worked because people were just that used to constant Flash security patches, most of which required a full reboot to apply; Chrome fixed both of those issues). Apple are the ones who ultimately dealt the death blow to Flash, and it was really just because Adobe could not optimize it for phone CPUs no matter what they tried (even the few Android releases of Flash that we got were practically unusable). That also further accelerated the adoption of open source HTML5 technologies.

PDF is an open source format, and has been since 2008. While I don't know if pressure from Google is what did it, that wouldn’t surprise me. Regardless, the Chrome PDF reader, PDFium, is open source[2] and Mozilla's equivalent project from 2011, PDF.js, is also open source.[3] Both of these projects replaced the distinctly closed source Adobe Reader plugin that was formerly mandatory for viewing PDFs in the browser.

Chrome is directly responsible for eliminating a lot of proprietary software from mainstream use and replacing it with high-quality open source tools. While they've caused problems in other areas of browser development that are worthy of criticism, Chrome's track record when it comes to open sourcing their tech has been very good.

[1]: https://blog.chromium.org/2011/01/html-video-codec-support-i...

[2]: https://github.com/chromium/pdfium

[3]: https://github.com/mozilla/pdf.js

Firefox Nightly is an unstable test version. You should report PDF issues to this GitHub repository.

Open this page and click on New Issue to ask the developers of the PDF viewer: mozilla/pdf.js repository. Please post a link to your question here.