![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
After updating to Firefox 32.0.3 Print Dialog box will not apear in XP/Win7Pro after a while but a restart of Firefox will allow it to show up again..
After automatically updating to 32.0.3 last Thursday and this Monday on all our Staff and Patron computers both Win7 pro and XP pro we have seen Firefox sessions that will not bring up the Print Dialog. The Print Preview dialog will come up but no print button or print menu item will bring up the Print Dialog. After you close Firefox and reopen it the Print Dialog box will work again for some time. The websites that Patron and Staff use during a session are different and done seem to be the cause. The Firefox settings are at fault because a simply restart of just Firefox fixes the issue and no other web browsers or application has any problem with displaying the Print Dialog at any time. Again this began on all the computers as soon as 32.0.3 was installed automatically over night.
Ŋuɖoɖo si wotia
Thanks Guigs2,
Our users ended up restaring Firefox so I could not get this info. Now it looks like the issue may have been fixed in v33.
Xle ŋuɖoɖo sia le goya me 👍 0All Replies (2)
Hi NPLD, Thank you for your question, I understand that there are multiple computers that no longer have a working print dialogue after a while of using Firefox. However after a restart, the print dialogue continues to act normally.
Does resetting the printing settings on the affected computers only temporarily change this as well?Fix printing problems in Firefox
I noticed it when I tested this page: http://www.housebeautiful.com/decorat.../1920s-home-before-after?src=spr_FBPAGE&spr_id=1451_94608649#slide-2 However I cannont reproduce it all the time. The print icon in the page has a opened a printable view and then the print dialoge comes up. When I switched to another program, that icon did not open the preview.
Do you notice any about:config entries that change when you see this start to happen?
Ɖɔɖɔɖo si wotia
Thanks Guigs2,
Our users ended up restaring Firefox so I could not get this info. Now it looks like the issue may have been fixed in v33.