搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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)