Conversations involving multiple participants, allowing collaboration and information sharing in Teams
still an issue
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
ft and right arrow keys have no effect in TEAMS BUT left-arrow + CTRL moves left one word, and right-arrow + CTRL moves right one word. So it is clear the arrow keys on the keyboard are functioning and sending signals to the computer. I also tried my laptop built in keyboard & the number pad. All have the same effect. What could be making the arrows by themselves not work? (Up and Down arrows work normally.)
1. Is it a laptop or desktop computer?
Laptop
2. What is the make and model of the keyboard?
HP laptop keyboard & logitech external
3. Was it working fine earlier?
Yes at most an hour before
4. Were there any recent changes made on the computer prior to the issue?
No. Maybe I inadvertently hit some hot key?
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.
still an issue
When the left/right arrow key got stuck, you can try to recover by doing these simple steps: (1) click any empty space inside the chat pane, (2) then click the "esc" key on your keyboard, and (3) finally click inside the compose box again where the arrow keys stuck. This should help you recover without the need to relaunch Teams client.
that does work, thank you!
How is this still not fixed?
It's been over a year since I started having this problem. Devs even got everything spoon-fed by now.
I could make a list with bugs that I encountered in Teams that have still not been fixed after a year+ later (Teams Status being displayed wrong as an example). New stuff keeps being added, new bugs keep appearing but apparently no one bothers himself to fix existing problems.
Wow! Finally someone has a simple fix! Thank you, Ben!