User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:32.0) Gecko/20100101 Firefox/32.0 Waterfox/32.0 Build ID: 20140903161535 Steps to reproduce: Attempted to print pdf from Firefox directly. Results did not match what was seen onscreen. http://www.newtec.eu/frontend/files/userfiles/files/Newsletters/Newtec%20Newsletter%20September%202014%20-%20Web-%20Lower%20Version%20-%202014-09-05.pdf try printing e.g. page. 11. Actual results: Text of heading (white text on red)was severely degraded with vertical lines missing; this seems to be pretty common with printing from Firefox. Edges were severely cropped, text was lost. Printing from Adobe Acrobat at the same time did not show these problems. Expected results: Should match screen. Should match printout from Adobe acrobat. Doesn't match screen. Doesn't match superior printout from Adobe acrobat. Seriously, pdf handling in Firefox remains a bad joke.
Created attachment 8493466 [details] on the left, printed from Firefox. On the right, printed from Adobe Acrobat. Note differences in text heading (vertical lines) and edge cutoff on right/bottom Shows differences in text heading (vertical lines) and edge cutoff on right/bottom
This is a followup on the same theme to bug 960398, bug 1050040, and countless others. The theme being that Firefox handles pdfs very very badly. If this can't be fixed, removing the pdf renderer from Firefox entirely is probably the best thing to do.
It's a false statement from you, Firefox doesn't render PDF badly, a bunch of bugs has been fixed since 2 years and most PDFs are well rendered for a daily use. On the other side, printing is not always correct but it's a known issue.
Issue about font sanitizer: "PDF 6ac270a8997076489fc2e4b046eb61bb [1.5 Adobe PDF Library 11.0 / Adobe InDesign CC 2014 (Windows)] (PDF.js: 1.0.801)" viewer.js:3534 downloadable font: cmap: Range glyph reference too high (2 > 1) (font-family: "g_font_8" style:normal weight:normal stretch:normal src index:0) source: data:font/opentype;base64,T1RUTwA(...) downloadable font: cmap: failed to parse table (font-family: "g_font_8" style:normal weight:normal stretch:normal src index:0) source: data:font/opentype;base64,T1RUTwA(...) downloadable font: rejected by sanitizer (font-family: "g_font_8" style:normal weight:normal stretch:normal src index:0) source: data:font/opentype;base64,T1RUTwA(...) downloadable font: font load failed (font-family: "g_font_8" style:normal weight:normal stretch:normal src index:0) source: data:font/opentype;base64,T1RUTwA(...)
Firefox renders pdfs badly. Firefox prints pdfs badly. Those are repeatedly provable facts. See attached photo taken today with recent print example. As I said in bug 960398 and in bug 1050040, Firefox's pdf rendering is simply dangerous to day-to-day work. It has a real problem with vertical lines, like 1 (which vanishes) or the downstrokes of M. It renders pdfs badly. pdf rendering and printing should be removed from firefox entirely. Or should be disabled. This has been years of problems, it's not going to get better, remove it.
Please try to be constructive in your comments. Bugs happen, and insulting the people who try to help fix the problem isn't really in your own interest. See also https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
Summary: printing pdf from firefox continues to be a bad joke. → clipped letters when printing PDFs
I am not insulting the people. I am stating how well Firefox pdf rendering works, and how badly it has worked over a large number of years without being fixed. That is an assessment of Firefox's capabilities, not of the people behind Firefox, on which I have made no comment. This is not ad hominem. "Firefox doesn't render PDF badly" is repeatedly and provably false. It does render pdfs badly - and badly enough that information printed from Firefox can be misleading and misread.
Priority: -- → P3
With latest Nightly 36.0a1 (e10s enabled) under Win 7 64-bit the pdf is correctly rendered, but printed as attachement shows. Set as new.
Status: UNCONFIRMED → NEW
Ever confirmed: true
With Firefox 40.0.3, printing output fails exactly as described in this bug, and does not match what is onscreen. So, no changes. This bug will shortly celebrate its first-year anniversary.
You need to log in before you can comment on or make changes to this bug.