Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Ctrl + B Moves Cursor to Beginning of Line

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by 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.

All Replies (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.