Closed Bug 172503 Opened 23 years ago Closed 22 years ago

Mozilla crashes when the printing is initiated by the website

Categories

(Core :: Printing: Output, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Thorsten_Reichelt, Assigned: rods)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 On this website a link let you printout the content. But not with Mozilla. Trying to print the page will cause Mozilla to crash. Reproducible: Always Steps to Reproduce: First go to: http://shop.mediamarkt.de/webapp/wcs/stores/servlet/ProductDisplay?productId=11201&catalogId=5000&langId=-3&storeId=5000&categoryId=10001 At the bottom of this page clcik on "Angebot drucken". A new window will open. Klick on "Drucken". Opera 6 has the same problem. With IE6 all works fine. Actual Results: The printing dialog will open and if you click on "print" Mozilla will crash and nothing is printed. Expected Results: Mozilla should print the site. Opera 6 has the same problem. With IE6 all works fine.
Need more details/confirm on a recent nightly. WFM on mapquest, which uses a javascript print function
WFM No crash on the site listed in the first issue report, and the page printed as well. Mozilla/5.0 (Windows; U; Windows NT 5.0; es-ES; rv:1.5) Gecko/20030916
works for me, is this still a problem?
This works for me as well: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040114
Resolving as WFM based on comments in bug. Reporter, if you're still experiencing the issue, please reopen, and supply as much information as you can about whats going on. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
reporter: if you can reproduce this with a current build, please run compopnents\talkback.exe and copy the incident id to this report. could you please indicate the printer name/model and driver version you were using?
You need to log in before you can comment on or make changes to this bug.