Created attachment 720710 [details] PDFviewerJS-FF19-Acrobat-pluginIE10.gif User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130215130331 Steps to reproduce: Testing a generated Financial Aid verification form PDF that was created using ActiveReports and Visual Studio, and meant to be viewed in the browser. Actual results: Headings and other bolded text was viewed and printed as being normal font weight instead of bold in Firefox 19 with PDF Viewer JS but appeared as expected in other browsers like Chrome or IE 10. Expected results: Headings and bolded text should have rendered bold in the viewer and in print. Attached image shows Firefox 19 PDF Viewer JS top (incorrect display) and IE 10 Adobe Acrobat plugin (expected display) bottom
Could you attach a PDF example, please.
Created attachment 721287 [details] Sample PF File When viewed in Firefox using PDFViewer.js it removes the bold and the italics text formatting from the PDF. When I print the PDF from Firefox using PDFViewer.js it prints like it looks o screen without the bold or italics text formatting. When viewed in other browsers using their default Acrobat plugin the PDF appears with bold and italics in place as expected.
The following info appear in the console: [14:22:44.768] PDF 18f64a3a634a63c5bc9b564586ddde4 [1.3 Data Dynamics ActiveReports (tm) for .NET / Data Dynamics ActiveReports (tm) for .NET] (PDF.js: 0.7.337) [14:22:45.039] Warning: The FontDescriptor's FontName is "Arial" but should be the same as the Font's BaseFont "Arial,Italic" [14:22:45.045] Warning: The FontDescriptor's FontName is "Arial" but should be the same as the Font's BaseFont "Arial,Bold"
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → jonas.jenwald
Whiteboard: [pdfjs-d-font-conversion] → [pdfjs-d-font-conversion][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/4578
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Depends on: 995431
Resolution: --- → FIXED
Target Milestone: --- → Firefox 31
You need to log in before you can comment on or make changes to this bug.