843558 - Firefox built-in PDF viewer doesn't support TCPDF

Status: RESOLVED FIXED

(Firefox :: PDF Viewer, defect)

Description

[Nino Vranešič [:elnino]]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20130220 Firefox/22.0
Build ID: 20130220031126

Steps to reproduce:

I tried  to open some example files of TCPDF which is PHP class for generating PDF documents using built-in PDF reader but it doesn't work as expected.


Actual results:

The PDF is not displayed correctly.


Expected results:

The PDF should have displayed correctly.

Comment 1

[Nino Vranešič [:elnino]]

Im providing you the links to examples: http://www.tcpdf.org/examples.php

Comment 2

[Nino Vranešič [:elnino]]

Attachment: Example no.1 opened with built-in PDF reader

Comment 3

[Nino Vranešič [:elnino]]

Attachment: Example no.1 opened with Adobe Reader

Comment 4

[Masatoshi Kimura [:emk]]

Web console says the font has been rejected by the platform.

Comment 5

[Sabine]

Example No. 15 with bookmarks doesn't work with the viewer, also not with google chrome. 
Normally you can set PDF bookmarks using the Bookmark() method and set PDF named destinations using the setDestination() method.
Before Firefox 19 the document was automatically opened with the Foxit-reader. On the left site of the pdf were  bookmarks. In the new Firefox built-in PDF viewer they are not shown.

Comment 6

[Christian Schmidt]

This issue is also being tracked in the pdf.js issue tracker:
https://github.com/mozilla/pdf.js/issues/2754

It seems to be related to HWA.

Comment 7

[Christian Schmidt]

The problem goes away if you disable font subsetting in TCPDF.

Comment 8

[Sabine]

I disabled font subsetting ($pdf->setFontSubsetting(false);) but this did not fix the bookmark-problem. 
@Christian Schmidt:
Was ($pdf->setFontSubsetting(false);) enough for you to fix the bookmark-problem or did you something else?

Comment 9

[Christian Schmidt]

My comment about font subsetting only related to the rendering problems as reported by Nino Vranešič.

The bookmark problem sounds like a separate issue, so I recommend that you create a separate bug report for that.