Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

搜索 | 用户支持

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

详细了解

Ctrl + B Moves Cursor to Beginning of Line

  • 2 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 TheBaron

more options

My wife and I both are using Tbird ver. 115.3.2 on our Windows 10 desktop computers. When typing a sentence in an email if one wants to bold a word prior to typing it, we press the Ctrl + B keys and then type the word, but on doing so the cursor jumps to the beginning of that line. It happens on both our computers. I checked and the Ctrl + B keys work normally in both Word and Excel. (That is, the cursor does not move.) Is there someway to stop the cursor from jumping under this scenario? Thanks.

My wife and I both are using Tbird ver. 115.3.2 on our Windows 10 desktop computers. When typing a sentence in an email if one wants to bold a word prior to typing it, we press the Ctrl + B keys and then type the word, but on doing so the cursor jumps to the beginning of that line. It happens on both our computers. I checked and the Ctrl + B keys work normally in both Word and Excel. (That is, the cursor does not move.) Is there someway to stop the cursor from jumping under this scenario? Thanks.

所有回复 (2)

more options

I am using Thunderbird 115 on Windows 11 on a desktop computer and Ctrl+B toggles the bold on the toolbar. Therefore I think we should be looking for something other than "Thunderbird" Try restarting Thunderbird from the help menu ion troubleshoot mode. When prompted, continue.

Still see the issue in Troubleshoot mode?

more options

Matt,

I put my Tbird in Troubleshoot Mode and tested the problem. It went away. That is, I could toggle Bold on, type the next word in bold and then toggle Bold off. Just as expected! I then took Tbird out of Troubleshoot Mode and, surprisingly, it also worked as it should. I did the same on my wife's computer with the same result. It seems like, as of this minute, the problem has gone away. For how long I don't know. Any further thoughts on why putting Troubleshoot Mode on and off would solve the problem? Thanks.