Closed
Bug 697153
Opened 14 years ago
Closed 11 years ago
Generated PDF files are unreadable
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: paulg, Unassigned)
Details
Attachments
(3 files)
I have run into a issue with Firefox 7.0.1. When I "print to a file" and select my output as PDF, the resulting PDF file is badly spaced, missing characters and totally unreadable. I have no problem with SeaMonkey 2.4.1 or Firefox 6.0.1
Thank you
| Reporter | ||
Comment 1•14 years ago
|
||
| Reporter | ||
Comment 2•14 years ago
|
||
| Reporter | ||
Comment 3•14 years ago
|
||
Comment 4•14 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:10.0a1) Gecko/20111027 Firefox/10.0a1
I can reproduce this on the Nightly only with http://store.apple.com/us
Tried printing with a wikipedia site, but couldn't reproduce.
STR used:
1. Start Firefox with a clean profile.
2. Load http://store.apple.com/us
3. Print to pdf.
4. Close Firefox.
5. Open the corresponding pdf file from the saved location.
I can not reproduce on Firefox 8Beta5, however, so probably the bug that triggered this issue has been backed out.
Paul, is this the same on your side? Do you have other Steps to reproduce? Does this issue occur when attempting to print other sites as well? Also, does it occur if following steps 1-4?
Moving to Core-Printing at the moment and waiting for some feedback.
Component: General → Printing: Output
Product: Firefox → Core
QA Contact: general → printing
Version: 7 Branch → Trunk
| Reporter | ||
Comment 5•14 years ago
|
||
I don't have any other step to reproduce and as far as I know I haven't been able to reproduce on any other site.
If I follow the steps listed below, I was unable to reproduce.
1. Start Firefox with a clean profile.
2. Load http://store.apple.com/us
3. Print to pdf.
4. Close Firefox.
5. Open the corresponding pdf file from the saved location.
I
Comment 6•14 years ago
|
||
Paul, does the bug also appear for you in a beta, aurora, or nightly build? I seem to recall something like this that depended on the exact fonts involved and got fixed somewhat recently....
If it still doesn't work in a current build, would you be willing to use http://harthur.github.com/mozregression/ to find when the problem appeared?
Comment 7•14 years ago
|
||
Paul: Can you answer Boris's question in Comment 6? You can get the latest Firefox Aurora or beta build from http://www.mozilla.org/en/firefox/channel/
Comment 8•11 years ago
|
||
no response
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•