This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When I am typing in the message/chat window and I want to go back using the arrow keys on my keyboard it doesn't work. The cursor doesn't move at all. I have to use the mouse to move the cursor. I am running Teams on Windows 11 22000.318, Teams version 1.4.00.29469 (64-bit).
On a side note, I have also noticed that typing the three ` no longer puts me into Code Snippet mode.
Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I think the most productive thing we can do to get this fixed is to figure out what causes the arrow keys to stop working. I thought it was when I used (Ctrl or Shift) + (left or right), but I am mistaken. I'll keep my eyes open. If I catch it, I'll post here.
This issue is so annoying. Ctrl ← and Ctrl → works but not ← nor → keys in chat.
Same here with arrow keys. Backspace usually works, navigation keys work intermittently. It is really frustrating not to be able to go back to correct a typo. Please do not ignore this and fix this issue in editor. It is most certainly error in text editor code that handles navigation keys.
This bug is several months old and terribly annoying. Ok, there are workarounds... however using the arrows is such a simple thing every user is familiar with that this bug is unacceptable.
It's a totally embarrassing bug for MS.
Your Team communication app can't use the keyboard properly when every other app, including MS apps, works just fine with the keyboard in the moment.
Teams is just a slow, somewhat unresponsive, client that needs to be re-written.