Avatar for Username

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信，及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

话题已存档。 如果需要帮助请提出新问题。

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

  • 1 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 Jonathan Watt

MikeDos
MikeDos
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

所有回复 (1)

Jonathan Watt
Jonathan Watt
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?