Closed Bug 1722036 Opened 4 years ago Closed 4 years ago

Incorrect rendering in Firefox PDF viewer (check box issues)

Categories

(Firefox :: PDF Viewer, defect, P1)

Firefox 91
defect

Tracking

()

VERIFIED FIXED
94 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- fixed
firefox92 --- wontfix
firefox93 --- wontfix
firefox94 --- verified

People

(Reporter: postmaster, Assigned: calixte)

References

(Regression)

Details

(Keywords: regression)

Attachments

(3 files)

Attached file test1.pdf

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

Recent update to Firefox v.90 (as well as in FF dev. edition v.91) caused an issue to show all check boxes are UNCHECKED by default in built-in FF PDF viewer.

Actual results:

The PDF doc was generated programmatically on webserver side based on a blank PDF doc with acrofields (template). The result is all check boxes and radio buttons are unchecked by default giving a corrupted output, supposedly a built-in pdf.js is changed as well.

Expected results:

Some check boxes should be checked. FF PDF viewer gives blank check boxes, the output is normal in Google Chrome, MS Edge browsers and Acrobat Reader. Please see attached file test1.pdf.

The Bugbug bot thinks this bug should belong to the 'Firefox::PDF Viewer' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → PDF Viewer
Status: UNCONFIRMED → NEW
Ever confirmed: true
See Also: → 1720411
Has Regression Range: --- → no
Has Regression Range: no → yes
Regressed by: 1693855

This might be related to the other regression of bug 1693855: bug 1715476.

The checkbox has /AS /a.m and /V /Off which means that its appearance is checked (see /AS) but its value is unchecked (see /V).
It's a bit confusing... for reference:

I opened this pdf in all the different pdf readers I have (acrobat included) and all of them except pdf.js are showing a checked checkbox. So it seems that AS matters first... and the documentation about V is a bit unclear for me, I mean I've the impress that V is just a dup of AS so why having it....

Assignee: nobody → cdenizet
Status: NEW → ASSIGNED

Setting severity to S3 because a possible workaround exists.

Severity: -- → S3
Priority: -- → P1
Commit merged into master by GitHub Authored by calixteman (calixteman)

It's not clear to me if this issue is fixed in pdf.js and if it is, if a new pdf.js release was done and shipped in Firefox. Calixte can you shed some light on this? Thanks

Flags: needinfo?(cdenizet)

The patch has been merged upstream but we didn't release a new version for now (the meta bug which tracks release is https://bugzilla.mozilla.org/show_bug.cgi?id=1626408).

Flags: needinfo?(cdenizet)
Depends on: 1732117
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED

I was able to reproduce the issue on Beta 91.0.
Verified as fixed on Windows 10/Ubuntu/Mac 10.15 using Beta (94.0b5).
Verified as fixed on Windows 10/Ubuntu using Nightly (95.0a1- 20211014).

Status: RESOLVED → VERIFIED
Flags: qe-verify+
Depends on: 1741445
Target Milestone: --- → 94 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: