ابحث في الدعم

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.

Learn More

Why does print and print preview take about 30 to 60 seconds to appear?

  • 1 (رد واحد)
  • 1 has this problem
  • 7 views
  • آخر ردّ كتبه Jonathan Watt

more options

I have tried the existing recommendations to delete item(s) beginning with print_ that had no effect. I copied prefs.js and removed all items beginning with print and replaced existing prefs file. Curiously that change worked at least twice before trying PDF print preview. After trying the preview the print function went back to taking 30 to 60 seconds to respond.

Print and print preview work fine in Chrome and Safari.

I have a macbook air and a new macbook pro. The macbook pro works well. I compared the config print items and found no obvious discrepancies. Both macbooks are on Firefox 84.0.2

My significant other blames Apple. I am convinced the problem lies with Firefox. Oh -- print screens are not worthwhile since we're talking a major time delay.

MikeDos

I have tried the existing recommendations to delete item(s) beginning with '''print_''' that had no effect. I copied prefs.js and removed all items beginning with '''print''' and replaced existing '''prefs''' file. Curiously that change worked at least twice before trying '''PDF print preview'''. After trying the preview the print function went back to taking 30 to 60 seconds to respond. Print and print preview work fine in Chrome and Safari. I have a macbook air and a new macbook pro. The macbook pro works well. I compared the config print items and found no obvious discrepancies. Both macbooks are on Firefox 84.0.2 My significant other blames Apple. I am convinced the problem lies with Firefox. Oh -- print screens are not worthwhile since we're talking a major time delay. MikeDos

All Replies (1)

more options

Hi MikeDos. This site is intended for helping end users with using Firefox, but what you're describing sounds like a bug. Would you mind reporting this over on the Mozilla issue tracker at https://bugzilla.mozilla.org/ where the developers would be better able to help you? If you do that, can you also mention over there which versions of macOS the macbook pro and macbook air are running?