fune/toolkit/components/pdfjs
2024-05-07 04:40:58 +03:00
..
content Backed out changeset e38f6abaf757 (bug 1895324) for causing pdfpaint failures. CLOSED TREE 2024-05-07 04:40:58 +03:00
test Backed out changeset 20b5e4b2f448 (bug 1877195) for breaking HTTP downloads (bug 1892069) 2024-04-18 17:20:00 +02: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 Bug 1855300 - convert .ini manifests to .toml: batch 11 remaining **/mochitest.ini r=jmaher,geckoview-reviewers,extension-reviewers,valentin,credential-management-reviewers,cookie-reviewers,sgalich,m_kato,robwu 2023-10-13 02:32:24 +00:00
moz.yaml Backed out changeset e38f6abaf757 (bug 1895324) for causing pdfpaint failures. CLOSED TREE 2024-05-07 04:40:58 +03:00
pdfjs.sys.mjs
README.mozilla
update.sh Bug 1894727 - Update pdf.js revision for talos tests with updatebot r=marco 2024-05-02 15:51:41 +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.