Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Firefox 88 - very slow to create print preview

  • 3 răspunsuri
  • 3 au această problemă
  • 1 vizualizare
  • Ultimul răspuns de egutwillig

more options

When I try to print from Firefox 88 on my Mac Laptop running OSX 10.12.6 the new print preview window takes a very long time to load the preview before I can print. I could not find a work around.

I tried switching to the Classic print system via (print.tab_modal.enabled - False) Now I don't have the preview to deal with so I can print immediately like I used to. However, if I try to open a PDF in Preview from the Print Dialog window, it takes a very long time to load the preview which it did not do in earlier versions of Firefox.

I am surmising that one of the Firefox updates added the print preview function which doesn't work quite right on my Mac.

Any ideas would be appreciated. Andy

When I try to print from Firefox 88 on my Mac Laptop running OSX 10.12.6 the new print preview window takes a ''very'' long time to load the preview before I can print. I could not find a work around. I tried switching to the Classic print system via (print.tab_modal.enabled - False) Now I don't have the preview to deal with so I can print immediately like I used to. However, if I try to open a PDF in Preview from the Print Dialog window, it takes a very long time to load the preview which it did not do in earlier versions of Firefox. I am surmising that one of the Firefox updates added the print preview function which doesn't work quite right on my Mac. Any ideas would be appreciated. Andy

Toate răspunsurile (3)

more options

Hi Andy, a couple versions ago, Firefox desktop users on Mac, Windows and Linux all got the same new unified print experience. Some users have reported that the preview does not generate or takes a long time to generate, but I don't know whether a pattern has been discovered for that.

In your experience, are particular sites or particular kinds of pages/documents much slower than the others?

Regarding the PDF, you are printing a web page to PDF in the native MacOS print dialog, and that is taking a long time to open in Preview after you save it? I don't know why that would, unless of course it's an unusually large file. ??

more options

Thanks for offering your thoughts I never noticed anything that ever made a difference when trying to print using the new unified print experience. It always took a very long time to complete the preview before I could print.

Are other Mac users having similar experiences? My guess is that the new Firefox versions and OSX are not happy together, but that's just a guess on my part.

Regarding creating a PDF from a web page using the System dialog. I just tried creating a PDF from a very short web page. It took a long time before the PDF icon appeared on my desktop. It used to happen very fast before the newer versions of Firefox showed up.

It is interesting that I have slow processing of print preview in the unified version and slow processing of PDF generation in the classic dialog. It seems to me it has to be a bug in Firefox. If that is the case, I wonder if there is any preference or setting that can help resolve this or does Mozilla need to troubleshoot the problem.

more options

The slow printing problem exists with osX Sierra 10.12 and possible other versions prior to 10.14.

The bug has bee reports numerous times but on one is working on a fix as of 10/16/21.

Probably no choice but to switch to another browser.