This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Etsi tuesta

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.

Lue lisää

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

  • 1 vastaus
  • 1 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja 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,

Valittu ratkaisu

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

Lue tämä vastaus kontekstissaan 👍 1

Kaikki vastaukset (1)

more options

Valittu ratkaisu

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