3 ms·
Given that Chrome/Edge also just added the feature, I would point out: All web browsers are using the same library for PDF handling, a feature in pdf.js ends up
by ocdtrekkie 6y ago
Given that Chrome/Edge also just added the feature, I would point out: All web browsers are using the same library for PDF handling, a feature in pdf.js ends up benefiting a lot of people.
And the reasons for not requiring an outside PDF reader are major: It's yet another likely-to-have-vulnerabilities program people need to install, then update. In most cases, avoiding Adobe programs on your PC is a good way to avoid a lot of vulnerabilities.
- oefrha 6y ago> All web browsers are using the same library for PDF handling Chrome/Chromium uses PDFium, not PDF.js, so no. Not sure about Edge. PDFium has been able to fill out forms for a long time. What’s new for Chrome is the ability to save edited PDF (as fillable).
- ocdtrekkie 6y agoIf Chrome doesn't use pdf.js, then neither would Edge, which is a Chrome fork. My original comment may have been mistaken.
- oefrha 6y agoA Chromium fork could replace certain components if they so choose. The PDF rendering component would be one of the easier ones to replace. However, I was able to confirm that Edge uses extension ID mhjfbmdgcfjbbpaeojofohoefgiehjai to render PDF internally[1], same as Chrome, so indeed it's using PDFium. [1] The rendered PDF element would look like <embed id="plugin" type="application/x-google-chrome-pdf" src="..." stream-url="chrome-extension://mhjfbmdgcfjbbpaeojofohoefgiehjai/..." headers="..." ...> And here's the extension's manifest in Chromium source, where you can find the extension ID: https://github.com/chromium/chromium/blob/2baa2b094cdd60e980c1e32c2535b57b700e337f/chrome/browser/resources/pdf/manifest.json https://github.com/chromium/chromium/blob/2baa2b094cdd60e980...