1779742 - Text not rendered in PDF viewer

Status: RESOLVED DUPLICATE of bug 1778692

(Firefox :: PDF Viewer, defect)

Description

[Adrian Florinescu [:aflorinescu]]

Attachment: PDF-3dtext.jpg

[Tracking Requested - why for this release]:
Seems to me that it's a pretty bad regression for the affected pdfs and should be fixed in 103 aswell.

Found in

• 103.0b9

Affected versions

• (not affected) 104.0a1 2022-07-14
• 103.0b9

Affected platforms

• Windows 10
• Mac 10.14
• Ubuntu 22.04

Steps to reproduce

1. Open https://tetra4d.com/wp-content/uploads/2018/12/PartList-Helico.pdf

Expected result

• PDF is opened in Firefox, all text is rendered and visible

Actual result

• Most of the data in PDF is not rendered in PDF viewer

Regression range

• First bad: 2022-06-19
• Last good: 2022-06-18
• Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c2a31813520bcb04cc99d0a3b823d876ae581d4d&tochange=ce6c834568c234e4d262bd4a648d68fdc2b58baf
• Potentially regressed by: Bug 1774899 - Update PDF.js to be2dfe45f96fa58a1926f764fd64d2416cecc501 r=pdfjs-reviewers,calixte

Note

• Not sure how reliable is but mozgression find fix points towards bug 1772941.

Comment 1

[Marco Castelluccio [:marco]]

Maybe this is the same as bug 1778692? Could you find the regression range in bug 1778692?

(In reply to Adrian Florinescu [:aflorinescu] from comment #0)

Note

• Not sure how reliable is but mozgression find fix points towards bug 1772941.

Most likely it isn't right. If it is the same as bug 1778692, then the fix is in bug 1778827.

Comment 2

[Adrian Florinescu [:aflorinescu]]

(In reply to Marco Castelluccio [:marco] from comment #1)

Maybe this is the same as bug 1778692? Could you find the regression range in bug 1778692?

(In reply to Adrian Florinescu [:aflorinescu] from comment #0)

Note

• Not sure how reliable is but mozgression find fix points towards bug 1772941.

Most likely it isn't right. If it is the same as bug 1778692, then the fix is in bug 1778827.

I can't confirm or infirm based on mozregression find fix - it is still pointing towards bug 1772941, but given that found commit message is a backout, I was guessing that it is mostly likely wrong. Indeed bug 1778827 seems more likely to be the fixing issue.

Comment 3

[Jonas Jenwald [:Snuffleupagus]]

Having just checked using the Debugger, in Firefox 103, this was indeed fixed by https://github.com/mozilla/pdf.js/pull/15153

Comment 4

[Calixte Denizet (:calixte)]

This a regression from https://github.com/mozilla/pdf.js/pull/15054 and it has been fixed thanks to https://github.com/mozilla/pdf.js/pull/15153.
The pdf is almost unusable, because it contains a lot of JS actions which are using some unimplemented JS features (Annot3D).

Comment 5

[Marco Castelluccio [:marco]]

Calixte, Jonas, do you think this might be common enough to require an uplift to 103?

Comment 6

[Ryan VanderMeulen [:RyanVM]]

I put a cherry-pick patch up in bug 1778692. Feel free to rubberstamp if you're on board with taking it :)

Comment 7

[Jonas Jenwald [:Snuffleupagus]]

(In reply to Marco Castelluccio [:marco] from comment #5)

Calixte, Jonas, do you think this might be common enough to require an uplift to 103?

It's difficult, at least for me, to speculate on how common this might be.
However, the patch is really simple and should be (completely) safe to uplift in my opinion.

Comment 8

[Calixte Denizet (:calixte)]

Same answer as Jonas one.