Open Bug 1563678 Opened 5 years ago Updated 10 months ago

Blocking web fonts prevent Firefox front displaying PDF documents correctly


(Firefox :: PDF Viewer, defect, P3)




Tracking Status
firefox67 --- affected
firefox68 --- affected
firefox69 --- affected
firefox70 --- affected


(Reporter: raphael.mozilla, Unassigned)



(Whiteboard: [pdfjs-font-missing])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Steps to reproduce:

Actual results:

PDF do not display correctly, like this one:

Expected results:

Fonts should still be loaded from PDFs. Blocking them in PDF seems useless and does not help accessibility / usability either.

(I block web fonts to save bandwidth, fonts included in PDFs are downloaded anyway)

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0


I have managed to reproduce this issue on latest FF release (67.0.4) and latest Nightly build 70.0a1 (2019-07-08) using Ubuntu 18.04 and Windows 10.
I will move this over to a component so developers can take a look over it. If is not the correct component please feel free to change it to an appropriate one.

Thanks for the report.

Component: Untriaged → PDF Viewer
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
Version: 60 Branch → Trunk

Change the status for beta to have the same as nightly and release.
For more information, please visit auto_nag documentation.

When web fonts are disabled we use a different font renderer in pdf.js. Seems like there's a problem with it for the above PDFs.

Priority: -- → P3
See Also: → 1752414
Whiteboard: [pdfjs-font-missing]

With FF 99.0, most of the text on appears as blank when font download is blocked. The text can be copied, though.

Severity: normal → S3
See Also: → 1796997

This issue is still present in FF 107.0. Another example: where the text is invisible, except for tt text and math symbols.

Duplicate of this bug: 1796997

I think we should follow what Jonathan suggested in bug 1796997 comment 11.

Duplicate of this bug: 1828488
See Also: → 1854090
You need to log in before you can comment on or make changes to this bug.