fune/toolkit/components/pdfjs
2022-08-15 20:06:50 +00:00
..
content Bug 1784918 - Update pdf.js to new version 518115fddc6db2c28752b8e9369c79377f521592 r=pdfjs-reviewers,Snuffleupagus 2022-08-15 20:06:50 +00:00
test Bug 1782254 - Add some telemetry to measure how often users are using the pdf editing feature r=Dexter 2022-08-09 17:38:37 +00:00
chrome.manifest
components.conf
jar.mn
LICENSE
metrics.yaml Bug 1782254 - Add some telemetry to measure how often users are using the pdf editing feature r=Dexter 2022-08-09 17:38:37 +00:00
moz.build
moz.yaml Bug 1784918 - Update pdf.js to new version 518115fddc6db2c28752b8e9369c79377f521592 r=pdfjs-reviewers,Snuffleupagus 2022-08-15 20:06:50 +00:00
pdfjs.js Bug 1667455 - Part 5: Stop importing Services.jsm from chrome-priv JS code, top-level single-line cases. r=kmag,webdriver-reviewers,perftest-reviewers,webcompat-reviewers,geckoview-reviewers,extension-reviewers,application-update-reviewers,pip-reviewers,twisniewski,m_kato,jdescottes,mconley,AlexandruIonescu,mossop 2022-07-11 12:41:50 +00:00
README.mozilla Bug 1783724: Fix nits in PDF.js's update script r=Snuffleupagus 2022-08-15 18:36:09 +00:00
update.sh Bug 1783724: Fix nits in PDF.js's update script r=Snuffleupagus 2022-08-15 18:36:09 +00:00

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.