搜尋 Mozilla 技術支援網站

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

了解更多

CSS “line-height” seems not working properly in TB60.3.0

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

more options

Hello

Since updating to TB60.3.0 (from 56.XX) I am facing a problem with my custom CSS.

Until now, I had a CSS file (userContent.css) with the “line-height” style defined as:

  • {font-size: 16px !important; font-family: Courier !important; line-height: 2em !important;}

and everything worked perfectly fine.

Since updating to TB60.3.0, when I compose a new message (in a new window), my custom line-height (2em) does not apply and message text remains with default setting (1em, I guess). While typing, the footer text jumps on the screen (like this - https://goo.gl/ACGZWS), showing something is wrong with line-height parametr.

The compose message window shows 1em line-height (as seen in the video) but when the message is sent (displayed in the main TB), the message text shows the correct 2em line-height.

The only moment when the custom line-height (2em) is not applied is the (live) message composing window.

Any suggestion how to fix this bug please?

Hello Since updating to TB60.3.0 (from 56.XX) I am facing a problem with my custom CSS. Until now, I had a CSS file (userContent.css) with the “line-height” style defined as: * {font-size: 16px !important; font-family: Courier !important; line-height: 2em !important;} and everything worked perfectly fine. Since updating to TB60.3.0, when I compose a new message (in a new window), my custom line-height (2em) does not apply and message text remains with default setting (1em, I guess). While typing, the footer text jumps on the screen (like this - https://goo.gl/ACGZWS), showing something is wrong with line-height parametr. The compose message window shows 1em line-height (as seen in the video) but when the message is sent (displayed in the main TB), the message text shows the correct 2em line-height. The only moment when the custom line-height (2em) is not applied is the (live) message composing window. Any suggestion how to fix this bug please?

所有回覆 (2)

more options

Has your message composition format switched from HTML to plain text, or are you just using a monospaced font as a matter of personal style?

Rules in userContent.css and userChrome.css files can be broken by changes to the CSS selectors used in the rules. I don't know what tools are available to investigate that angle.

more options

jscher2000 said

Has your message composition format switched from HTML to plain text, or are you just using a monospaced font as a matter of personal style?

Message composition format = plain text Using "Courier" font in custom CSS = intentional (matter of style)