We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

ابحث في الدعم

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

No longer able to Print Messages since updating to ver. 45

  • 1 (رد واحد)
  • 1 has this problem
  • 1 view
  • آخر ردّ كتبه Matt

more options

Problem #2 since updating to T-bird version 45:

Sometimes I like to compose a message then print a copy before sending. Prior to 45 I would do the following:

1) Click the "Write" button to start a new message. 2) Type and spell check my message. 3) Press Ctrl+P to open Print dialog box. 4) Select the printer (sometimes laser, sometimes pdf). 5) Click OK and done.

Since updating to ver. 45, I can only get to step 2. Unable to open the Print dialog box using any of the standard methods.

Is this a bug that will be fixed? Is there a work around? As I use this process many times throughout the day should I roll back to the previous version of T-bird?

thanks for your support,

Problem #2 since updating to T-bird version 45: Sometimes I like to compose a message then print a copy before sending. Prior to 45 I would do the following: 1) Click the "Write" button to start a new message. 2) Type and spell check my message. 3) Press Ctrl+P to open Print dialog box. 4) Select the printer (sometimes laser, sometimes pdf). 5) Click OK and done. Since updating to ver. 45, I can only get to step 2. Unable to open the Print dialog box using any of the standard methods. Is this a bug that will be fixed? Is there a work around? As I use this process many times throughout the day should I roll back to the previous version of T-bird? thanks for your support,

الحل المُختار

Yes it is a bug that will be fixed, in about a week with V45.1

Read this answer in context 👍 1

All Replies (1)

more options

الحل المُختار

Yes it is a bug that will be fixed, in about a week with V45.1