Mozilla 도움말 검색

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

자세히 살펴보기

68.3.1 completely borked fixed-width font usage

  • 2 답장
  • 1 이 문제를 만남
  • 24 보기
  • 최종 답변자: eric50

more options

After upgrading from 60.9.1 to 68.3.1 font usage, especially for fixed--width/plain text usage is borked. 1) The font size shrank a *lot* in both message display and composition. 2) The font in message bodies no longer matches that of the title bars, menus, etc. This is *ugly*. 3) The Options and config editor don't seem to be able to change the font size where I would expect based on the option name. 4) There doesn't seem to be a way to compose plain text messages in a fixed width font.

What the heck happened???

After upgrading from 60.9.1 to 68.3.1 font usage, especially for fixed--width/plain text usage is borked. 1) The font size shrank a *lot* in both message display and composition. 2) The font in message bodies no longer matches that of the title bars, menus, etc. This is *ugly*. 3) The Options and config editor don't seem to be able to change the font size where I would expect based on the option name. 4) There doesn't seem to be a way to compose plain text messages in a fixed width font. What the heck happened???

모든 댓글 (2)

more options

There are probably about 10 people left who use fixed width plain text emails.

But lets look at the options. Options > General > send options button. Do you have Send massage as plain text when possible selected? Do you have any HTML or plain text domains set?

Options > display > Formatting > Advanced button

Set you display fonts as you like them. Disallow messages to use other fonts Select use fixed width font for plain text message.

more options

Sorry, I tried all that and it had no effect.

After much teeth-gnashing I found the magic settings in the config editor to fix the font name in both display and composition. The config editor settings for size worked in composition but didn't have any effect in display, but ctrl-+ in the display fixed that.

I *really* *really* hope the next update doesn't screw things up this badly again.