Closed Bug 819988 Opened 12 years ago Closed 9 years ago

Print result of Web pages are white pages

Categories

(SeaMonkey :: General, defect)

SeaMonkey 2.14 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rschelp, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20100101 Firefox/17.0 SeaMonkey/2.14.1
Build ID: 20121129191119

Steps to reproduce:

Want to print, from "Print" command or print buttons included on some page (e.g. home banking and similar)


Actual results:

Print result are white pages. Printer is HP CP1025nw, but same happens while printing pdf documents using doPDF v6 or Software995 pdf printer. Same happens for browser and mail window.


Expected results:

Well ... I may think it should print ..., in any case, SeaMonkey is speaking Spanish, OS is MS XP SP3 with latest upgrades, running on a Core Duo with 4 Gb RAM. No other programs have problems regarding their print command
NOT reproducible  with EN-US SeaMonkey 2.33.1 (German Language pack)  Gecko/20100101 Build 20150321194901 (Classic Theme) on German WIN7 64bit

@Reporter: Still a problem for you? If “yes”, please contribute a problem related step by step instruction containing every key press and every mouse click how to reproduce your problem due to <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>    (similar to report in Bug 1139273)
Flags: needinfo?(rschelp)
Summary: No printing → Print result of Web pages are white pages
No response, so I close this one for now.
@Reporter: Please feel free to reopen this Bug if you still can reproduce the problem with a current SeaMonkey version and a current OS and if you can contribute a step by step instruction due to <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>  (containing every key press and every mouse click) how to reproduce the problem reliably.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.