Try : http://kb.mozillazine.org/Problems_printing_web_pages and https://support.mozilla.org/en-US/kb/fix-printing-problems-firefox

You do not name your printer so should go to maker and find the model and see if there is any updated Drivers or Flashes for it. If used a CD to install drivers those were outdated before opening the box. If Win10 is supplying your Drivers for it good, if Win10 has replaced your Drivers, bad. Win10 can and will change your hardware drivers to Microsoft's. https://www.howtogeek.com/302595/how-to-stop-windows-10-from-automatically-updating-hardware-drivers/

Final release of Firefox is tomorrow so should figure out what happens with your Beta/RC

Please let us know if this solved your issue or if need further assistance.

Hi, and thanks for your reply. I am using an HP 1200. It worked perfectly with the prior version of Firefox, 56.02. I am using Windows 8.1 so the Windows 10 info doesn't apply. I downloaded the Firefox 57.0 through MajorGeeks. There was no mention of it being a beta (I had been following the beta and nightly iterations without trying them).

And I will wait for tomorrow to see if there is a newer or real version of Firefox 57 that will take care of this printer problem. (Oh, and by the way, my workaround was to fire up Chrome and print through that.)

Did you check the HP site. Drivers dated Sep 26, 2017 are there. https://support.hp.com/ca-en/drivers/selfservice/hp-laserjet-1200-printer-series/29789

You can try to set this pref to 0 on the about:config page to lower the sandbox security setting.

• security.sandbox.content.level = 0
• close and restart Firefox to make the change effective.

if this didn't work then undo/reverse the change and reset the pref via the right-click context menu to the default value.

Thank you for trying.

LloydA said

And I will wait for tomorrow to see if there is a newer or real version of Firefox 57 that will take care of this printer problem. (Oh, and by the way, my workaround was to fire up Chrome and print through that.)

Why wait for Mozilla Servers tomorrow. Firefox Full Version 57 https://fileforum.betanews.com/detail/Mozilla-Firefox-for-Windows/1032985422/1 ( I used it, is not a beta, they just get it a day before release, my daily fix site..lol) .

Might want to uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files and C:\Program Files(x86) Then restart system. Then run Windows Disk Cleanup. Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved.

Please let us know if this solved your issue or if need further assistance.

So strange. My Windows 10 laptop updated to Firefox 57.0 today. The print function from FF 57 works perfectly -- yet my HP1200 printer (now with updated USB drive) is physically attached to the Windows 8.1 machine, which the laptop accesses through my wired/wifi network. It's FF 57 on the 8.1 desktop which prints blank pages.

PkShadow -- do you think that uninstalling FF 57 and going through the somewhat involved process you outlined will actually work? Have there been any other people who have experienced this problem that you know of?

Thanks, all, for your suggestions.

I am having same problem: FireFox 57.0 on my Win10 PC only prints blank pages on my HP4630. All drivers up-to-date, other applications (including Chrome Browser) print OK. Tried "security.sandbox.content.level = 0" fix, and emptying "...appdata/LocalLow/Mozilla/Temp" folder but still not printing.

Need fix!!!

BKSmith714 (number of Babe Ruth home runs?) At least I'm not the only one. I bet more people are having the problem. Oh ... and if I had opted to print more than one page at a time, only one page comes out blank, and then I get a "printer error" pop-up.

I hope to have a home run when I get a viable solution! I also get the pop-up printer error message after 1 page,

I did get a response - the normal "Do a Firefox reset" suggestion which, if after a couple of days, a more pointed solution is not proposed. It's a pain to have to reload add-ons and re-establish the customizations. We'll see.