Conversations involving multiple participants, allowing collaboration and information sharing in Teams
This worked for me too.
How bizarre!
Thanks for the post.
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.
This worked for me too.
How bizarre!
Thanks for the post.
I also experience this problem from time to time... Not being the perfect typist, this causes me no end of pain...
Please get it fixed.
Kaine
How can this still be an issue after this long? Note that the workaround of tabbing out of the box and back in worked for me, so it's clearly a bug in Teams. Fix it!
Thanks. Worked for me! :-)
Weird workaround that can be used while we are waiting for MS to fix this bug!
BINGO, almost.
Tab to move to the tools panel, lrlrlrl shift-tab did not restore L or R arrow keys.
Tab to move to the tools panel, activating the '...' item, then ESCaping, then shift-tab did restore L and R arrow functions.
The MS-Teams Chat textbox looks like it's got an unchecked state problem.
Just repeating the best workaround to date here.