PDF.js shows an "x" in checkboxes in editable forms, even when the page has another glyph that it wants to use to represent the check
Categories
(Firefox :: PDF Viewer, defect, P3)
Tracking
()
People
(Reporter: csasca, Unassigned)
References
Details
Attachments
(2 files)
Found in
- Firefox 109.0b7
Affected versions
- Firefox 109.0b7
- Firefox 110.0a1
Tested platforms
- Affected platforms: macOS 13.1, Windows 11, Ubuntu 22.04
Steps to reproduce
- Launch Firefox
- Access this PDF sample
- Tick some checkboxes from the Payment method
- Print the edited page to PDF
Expected result
- The checkboxes have "x" inside when selected
Actual result
- The checkboxes have a bolded "-" inside
Regression range
- Will see for a regression.
Additional notes
- The issue can be seen in the attachment.
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
This doesn't seem to be a regression as it was introduced along with the ability to edit forms in PDF files (late 2020 builds).
Comment 2•1 year ago
•
|
||
This is still reproducible with the linked PDF (and can be seen in e.g. Print Preview too). I suspect this is a bug in PDF.js rather than in the platform printing pipeline --> Reclassifying.
Comment 3•1 year ago
|
||
Here's the testcase saved from https://eforms.com/download/2019/01/Business-Receipt-Template.pdf , so that we've got it available for testing if it happens to disappear from the original site.
Comment 4•1 year ago
|
||
In the pdf the mark used to check the box is thick dash but the way we render it is always this X.
Ideally we should create some canvas containing the draw of the mark and use them depending on the button state.
Comment 5•1 year ago
|
||
(In reply to Calixte Denizet (:calixte) from comment #4)
In the pdf the mark used to check the box is thick dash but the way we render it is always this X.
Ah right, Chrome just directly shows the thick dash when you edit the PDF and check/uncheck the box.
So the print output has the correct rendering here, and the interactive rendering is the one that's technically wrong.
Comment 6•1 year ago
|
||
--> clarifying summary, and clearing "affected" statuses that are too old to be relevant at this point.
This might also be the same as bug 1802506 (where the PDF actually wants an "X" rendering in a control that visually looks like a checkbox, but we insist on drawing a radio button, because in that case the widget is functionally a radio-button under-the-hood).
Updated•1 year ago
|
Description
•