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.
Simple interactions, such as editing typos, missed contractions and spellings errors is frustrating.
I really struggle to see how this problem is still with us.
How is their premier collaboration and communication client if you can't navigate your written words?
I wonder if the fact that this issue has survived so many updates and has persisted for so long is somehow evidence that Microsoft doesn't actually use Teams for their own internal chat? How would the developers cope with this kind of bug? Don't most or all developers, as power users, use arrow keys to navigate code to prevent having to stop, find the mouse, find the mouse cursor, select the correct location very carefully, and then find the home-row keys again? I think this might be evidence of that. Just a thought.
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.
Hello!
This has been an ongoing issue for me for the last year. Almost every person in my office has reported the same issues. I first started noticing this bug in July of 2021. I have used multiple computers since then and I have still ran into this issue. Restarting the app/computer will fix temporarily.
This is something that needs to be addressed as it is very annoying to not be able to do all my typing and formatting with the keyboard.
Thanks,
Jayden