Skip to content

Checked checkboxes in acroform are printed in white #12046

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
calixteman opened this issue Jun 30, 2020 · 1 comment
Closed

Checked checkboxes in acroform are printed in white #12046

calixteman opened this issue Jun 30, 2020 · 1 comment

Comments

@calixteman
Copy link
Contributor

Attach (recommended) or Link to PDF file here:
https://www.irs.gov/pub/irs-pdf/f1040.pdf

Configuration:

  • Web browser and its version: firefox
  • Operating system and its version: debian testing
  • PDF.js version: master
  • Is a browser extension: no

Steps to reproduce the problem:

  1. Run acroforms example (https://github.com/mozilla/pdf.js/tree/master/examples/acroforms)
  2. Check some checkboxes
  3. Print the result in a file (sorry I've no printer)

What is the expected behavior? (add screenshot)
Having some checked boxes in the printed pdf

What went wrong? (add screenshot)
The crosses are printed in white so they're invisible

@Snuffleupagus
Copy link
Collaborator

Snuffleupagus commented Mar 25, 2021

Run acroforms example (https://github.com/mozilla/pdf.js/tree/master/examples/acroforms)

First of all, I don't think that example ever really "supported" printing, given all the hoops we have to jump through for printing to work in the default viewer; via web/firefox_print_service.js respectively web/pdf_print_service.js.
The only way to get printing to work, in that example, would thus have been to essentially re-implement printing similar to those files.

Secondly, that example has now been removed (see PR #13053), and effectively "replaced" by the regular viewer-component examples, since it was old and didn't illustrate best practices.

All-in-all, it seems that we should just close this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants