The pdf.js Digital Signature Properties UI (toolbar badge + doorhanger
panel) currently has no automated coverage. This adds two
browser-mochitest tasks against bundled signed PDFs:
- `test_signed_verified_pdf_renders_verified_panel` opens
file_pdfjs_signed_verified.pdf, waits for the toolbar button to
settle into `.state-verified`, opens the panel and asserts that the
verified banner, verified status row and trusted-certificate row
are all rendered with the expected Fluent ids.
- `test_signed_invalid_pdf_renders_invalid_panel` opens
file_pdfjs_signed_invalid.pdf, waits for the toolbar button to
settle into `.state-error`, opens the panel and asserts that the
invalid-signature banner and invalid status row are rendered, and
that no certificate row is shown (signerCertificate is intentionally
omitted when the signature itself is invalid).
Both tasks run with `pdfjs.enableSignatureVerification=true` and
`security.pdf_signature_verification.enable_test_trust_anchors=true` so
the bundled test fixtures validate against the `pdf-sign-ca` test trust
anchor without affecting the live root store.
The fixtures are reduced versions of the corpus used to exercise the
verification logic; both are below 12 KiB.
Differential Revision: https://phabricator.services.mozilla.com/D309699
Benjamin Beurdouche
46e0a7eb24
