User Agent: Mozilla/5.0 (Windows NT 10.0; rv:49.0) Gecko/20100101 Firefox/49.0 Build ID: 20160922113459 Steps to reproduce: I recently upgraded my desktop OS to Windows 10 ver. 1607. I can no longer print pages from Firefox ver. 49.0.1. My printer is an HP Officejet 6700 and it is directly connected, via USB, to my desktop PC. Actual results: I selected print from a Firefox web page and it appeared to direct the output to the correct printer but nothing came out on the printer and there were no error messages. Nothing is sitting in the print queue. Expected results: I tried printing the same pages using IE ver. 11 and they printed just fine, as expected, without having to reset anything or change anything.
Did you try to update print driver for Win 10? Can you give the printer driver version?
Component: Untriaged → Printing: Output
Product: Firefox → Core
I checked and I have the current printer driver from HP for my printer. Its ver. 28.8, file name is OJ6700_1315-1. However, this wouldn't explain why the printer still works with IE 11?
Further to above, I find that I can usually print from Firefox after all. There is one app I cannot print from at this site: https://apps.facebook.com/wonderword/?fb_source=search&ref=br_tf. Its a Wonderword puzzle available on Facebook and I find I can no longer do a print from the manual screen. I believe this app uses Adobe Flash Player. I checked and my PC is running ver. 184.108.40.206 which is the current release. So, perhaps my only solution at the moment is to print this app from IE.
If it is from Flash om Windows 10 see also: https://bugbase.adobe.com/index.cfm?event=bug&id=4183560
Is this still happening for you, Don?
Summary: I recently upgraded my desktop OS to Windows 10 ver. 1607. I can no longer print pages from Firefox. No error messages are displayed, just no printer action. If I switch to IE ver. 11, printing works fine. I am using Firefox ver. 49.0.1 → Printing Wonderword puzzle available on Facebook silently fails
You need to log in before you can comment on or make changes to this bug.