fune/toolkit/components/pdfjs
2023-03-21 11:15:46 +02:00
..
content Bug 1823360 - Update PDF.js to new version 3903391f3cbed25806adc4a9874979f7725ec883 r=pdfjs-reviewers,marco 2023-03-20 12:29:51 +00:00
test Backed out changeset 163d0d505694 (bug 1821408) for causing failures in browser_pdfjs_filters.js. CLOSED TREE 2023-03-21 11:15:46 +02:00
chrome.manifest
components.conf
jar.mn Bug 1803188 - Plug the pdf.js search feature in GeckoView r=pdfjs-reviewers,geckoview-reviewers,m_kato,marco 2023-01-30 19:14:46 +00:00
LICENSE
metrics.yaml Bug 1817107 - Update lifetime of some pdf.js metrics r=marco 2023-02-24 17:08:59 +00:00
moz.build Bug 1754499 - Add pdf.js in GeckoView r=geckoview-reviewers,pdfjs-reviewers,marco,m_kato 2022-11-24 13:36:17 +00:00
moz.yaml Bug 1823360 - Update PDF.js to new version 3903391f3cbed25806adc4a9874979f7725ec883 r=pdfjs-reviewers,marco 2023-03-20 12:29:51 +00:00
pdfjs.js
README.mozilla
update.sh

This is the PDF.js project output, https://github.com/mozilla/pdf.js

The current upstream commit is documented in the revision field in moz.yaml

To update PDF.js locally, run
	./mach vendor toolkit/components/pdfjs/moz.yaml
 
To avoid cloning PDF.js locally for every invocation of that command, you can
point ./mach vendor at a local repo by setting the PDFJS_CHECKOUT env var.
The update process will perform a git fetch and checkout the latest version to
update to, so any uncommited local changes will cause the update script to break.