为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

In TB, how do I make the printer "system dialog" standard for all printing?

  • 2 个回答
  • 0 人有此问题
  • 4 次查看
  • 最后回复者为 gp

more options

I reported long ago as a bug that Thunderbird (and Firefox) in my Ubuntu Studio 22.04 installation do not understand my printer's paper sizes. For a while I could get around this with the configuration option: print.tab_modal.enabled false because the system print dialog lists the appropriate sizes, but this no longer works. Now I have to first click the corresponding button in the Mozilla modal print dialog to select a standard paper size (e.g. A4) in the system print dialog. How can I suppress the useless modal print dialog and go directly to the system print dialog?

I reported long ago as a bug that Thunderbird (and Firefox) in my Ubuntu Studio 22.04 installation do not understand my printer's paper sizes. For a while I could get around this with the configuration option: print.tab_modal.enabled false because the system print dialog lists the appropriate sizes, but this no longer works. Now I have to first click the corresponding button in the Mozilla modal print dialog to select a standard paper size (e.g. A4) in the system print dialog. How can I suppress the useless modal print dialog and go directly to the system print dialog?

所有回复 (2)

more options

P.S. The problem with the wrong paper sizes in the modal print dialog appears to have been solved in Firefox (as of 109.0.1). Why hasn't the fix been implemented in Thunderbird?

more options

rsbrux said

P.S. The problem with the wrong paper sizes in the modal print dialog appears to have been solved in Firefox (as of 109.0.1). Why hasn't the fix been implemented in Thunderbird?

Hello

As far as I know, Thunderbird is not based on latest Firefox code - if you look at 'More troubleshooting', 'about:BuildConfig', you will find a reference to 'Mozilla-esr102'; that's a long term release for organizations wanting stability over latest features. So for your fix to appear, it will have to be 'backported', that is, retrofitted in older code. That's not always easy and while it is always done with security problems, it's not always the case with other problems, often those affecting a lot of people, and even then it may be postponed because other problems seem more urgent. Hmm, it seems that the release cycle for ESR is about 42 weeks, so if you are patient enough you will get the fix when the new major version ESR is released. Quote: "Firefox 102 was released on June 28, 2022" so in 2-3 months maybe ?