Closed Bug 1643322 Opened 4 years ago Closed 4 years ago

PDF Print Text Corruption - PDF.JS

Categories

(Firefox :: PDF Viewer, defect)

76 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jonathan.wilkins, Unassigned)

Details

(Whiteboard: [pdfjs-d-printing])

Attachments

(2 files)

161.51 KB, application/pdf
Details
319.63 KB, application/pdf
Details
Attached file bad-1.pdf

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36

Steps to reproduce:

At this time I cannot attache the original PDF or printed sample. It contains sensitive customer data. I am working to create a non-sensitive version of this issue and will append it to this issue. I will attempt to provide sufficient detail in the meantime.

Problem:
When PDF is printed (physically or to PDF), some text fields become corrupted, resulting in strings with new characters as well as missing characters.

Details:

PDF's created via FOP 2.3
Only occurs on multi-page PDF's
Multi-page PDF's are created by stitching together multiple existing PDF's (via PDFBox)
Only noticed in bold fonts using embedded font subsets.
Occurring often in production, obstructing USPS tracking numbers & other critical information
Configuration:

Firefox 76.0
Mac OS 10.15.4, Windows 10 1909
Steps to reproduce the problem:

Open PDF in Firefox (pdf.js).
initiate print via button or menu.
Print to paper or to pdf.
Observe bold text fields. Notice the overlapped text in the string that is supposed to be "USPS Tracking". Also notice the introduction of alpha characters like 'K' into the tracking number string below the barcode which is supposed to be all numeric.

Actual results:

Pages were printed. Third page contained corrupted text in several areas.
See page three bad-1-print.pdf, text just above the 1D tracking barcode. Should say "USPS TRACKING #"
See page three bad-1-print, text above sender address. Should say "USPS FIRST-CLASS PKG"
See page three bad-1-print, text in small box between addresses. Should say "R005".

Expected results:

Expected text should have appeared on page three problem areas.

Attached file bad-1-print.pdf

added bad print sample

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → PDF Viewer

The severity field is not set for this bug.
:bdahl, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(bdahl)
Severity: -- → S2
Flags: needinfo?(bdahl)
Whiteboard: [pdfjs-d-printing]

Following up on this.

Hi Jonwilks, I was able to reproduce this issue in our Release version of Firefox 76.0 on a mac 10.15, but I can no longer reproduce the issue in our latest FX 85.0.1, can you please try this issue on your end as well and see if it still occurs ? this may have already been fixed by a different issue.

You can find the build here:
https://www.mozilla.org/en-US/firefox/new/

Flags: needinfo?(jonathan.wilkins)

(In reply to Rares Doghi from comment #5)

Hi Jonwilks, I was able to reproduce this issue in our Release version of Firefox 76.0 on a mac 10.15, but I can no longer reproduce the issue in our latest FX 85.0.1, can you please try this issue on your end as well and see if it still occurs ? this may have already been fixed by a different issue.

You can find the build here:
https://www.mozilla.org/en-US/firefox/new/

I can confirm that the issue is NOT reproducible in FF85. Please resolve if you see fit.

Any idea where this may have been resolved? I assume this is a PDF.JS issue?

Flags: needinfo?(jonathan.wilkins)

Yes , I was able to get a regression range for this issue :

25:33.78 INFO: First good revision: 62c8ae7d2c524a0e2caf2559355f54530d6e78ce
25:33.78 INFO: Last bad revision: ac468fb1ea9db6653e39c5fcfbaebea8ac07673b
25:33.78 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ac468fb1ea9db6653e39c5fcfbaebea8ac07673b&tochange=62c8ae7d2c524a0e2caf2559355f54530d6e78ce

It seems that Bug 1646176 is the one that Fixed it.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: