Avatar for Username

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

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

  • 2 답장
  • 0 이 문제를 만남
  • 4 보기
  • 최종 답변자: gp

rsbrux
rsbrux
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)

rsbrux
rsbrux 질문자
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?

gp
gp
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 ?