Closed
Bug 552174
Opened 14 years ago
Closed 5 years ago
can NOT print contents of some open windows to printers or to .pdf files
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: lester.shulman, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 I am unable to directly print the content of open windows to either a pdf flie or to Lexmark series 7300 or 9300 printers from URLs. To print content I need to select all, copy to TextEdit, and then print or save from TextEdit. Other sites seem OK with v3.6. Reproducible: Sometimes Steps to Reproduce: 1.Print (from menu or apple P) 2.PDF button then "Save to pdf" 3.enter file name and then Save Actual Results: single blank page with header (file name and URL address) plus footer (page 1 of 1 and date and time) Expected Results: page with header and footer and all of content (text and graphic) from the window This problem always happened with the last version of firefox 3.5.x. It now happens only on some pages with v3.6. (for example http://www.jpost.com/) but apparently not on other pages (http://www.nytimes.com/) .
I have a same/similar issue except it won't print at all. Gives some sort of error and a window with a bunch of garbled text and a message that printing to pdf failed. This is a serious issue when trying to print emails. I have to log into the web interface for my IMAP email in order to do so. Using 3.1.7 with Adobe Acrobat Professional 8.0 installed, and printing to the pdf printer.
Updated•13 years ago
|
Version: unspecified → 3.6 Branch
Comment 2•5 years ago
|
||
Unfortunately we never diagnosed this at the time it was filed and much has changed since then. If it is still an issue in the latest Firefox, please feel free to re-open and update us on the status.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•