Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Print dialog: Odd behaviors with drop-down lists

  • 1 回覆
  • 2 有這個問題
  • 3 次檢視
  • 最近回覆由 em

more options

When I try to print, the drop-downs in the dialog for selecting the printer, page size, etc. look rather bizarre. The choices in each drop-down have missing letters. If I then hover the mouse over the list of choices, they appear normally.

This occurs with both Firefox and Thunderbird. It does not seem to happen with other applications (MS Office, etc.)

Attached are images to illustrate this, before and after mouse hover.

Any suggestions?

When I try to print, the drop-downs in the dialog for selecting the printer, page size, etc. look rather bizarre. The choices in each drop-down have missing letters. If I then hover the mouse over the list of choices, they appear normally. This occurs with both Firefox and Thunderbird. It does not seem to happen with other applications (MS Office, etc.) Attached are images to illustrate this, before and after mouse hover. Any suggestions?
附加的畫面擷圖

所有回覆 (1)

more options

I observe the same behavior described and illustrated by Birdbrain. I'm using Firefox version 93 on Windows 10 computer. I think the odd behavior started with version 93 but not sure if Windows could have anything to do with it. Definitely didn't have the problem behavior until after that 93 update. All other applications outside the Firefox container/browser on this computer work fine with the drop-down objects they utilize.

Within that Firefox print dialog open, scrolling down to the very bottom of the dialog, directly above the "save" and "cancel" buttons, there's the hyperlink to "Print using system dialog...". which opens a Windows print dialog and perhaps could be more or less useful as a workaround.

Hopefully this reported problem will be prioritized soon by Mozilla development for improvements.