fune/toolkit/components/pdfjs
2024-03-21 21:31:52 +00:00
..
content Bug 1886872 - Update PDF.js to new version 067c49dc49ce37ea99106f7d836456025f7ef5f4 r=pdfjs-reviewers,marco 2024-03-21 21:31:52 +00:00
test Bug 1864896: Autofix unused function arguments (toolkit). r=mconley,translations-reviewers,omc-reviewers,aminomancer 2024-03-19 14:59:21 +00:00
chrome.manifest
components.conf
jar.mn Bug 1883901 - Update PDF.js to new version 6bb6ce6a5d133c5aa318e2fff9d1df5326a1ea96 r=pdfjs-reviewers,fluent-reviewers,marco,flod 2024-03-06 21:29:04 +00:00
LICENSE
metrics.yaml Bug 1866437 - Add some telemetry for the highlight feature in pdf.js r=pdfjs-reviewers,marco 2024-02-29 12:42:29 +00:00
moz.build
moz.yaml Bug 1886872 - Update PDF.js to new version 067c49dc49ce37ea99106f7d836456025f7ef5f4 r=pdfjs-reviewers,marco 2024-03-21 21:31:52 +00:00
pdfjs.sys.mjs
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.