May 29 2024 06:00 AM
Hi,
I Report a bug when hovering a reaction on a message to view who's reacted to (Windows 10).
Sometimes, with the new Teams version (24102.2223.2870.9480.), hovering over a message's reaction causes the chat list to switch from the current one to a random one in your chat history.
OS:
Edition Windows 10 Enterprise
Version 22H2
Installed on 01-Jul-22
OS build 19045.4412
Experience Windows Feature Experience Pack 1000.19056.1000.0
May 29 2024 06:03 AM
Jun 05 2024 05:12 PM
Jun 11 2024 12:21 AM
So far I have not noticed any specific actions that lead to a change of chat, it is always a random chat or group
Jun 18 2024 08:55 PM
Jul 01 2024 03:45 AM
"me too".
In my case, I have a couple of "pinned" group chats, had just added a "fingers crossed" reaction to a colleague's message and was moving the mouse away when "suddenly" Teams switched to the top-most non-pinned chat.
I've got teams version 24152.412.2958.9166 and client 49/24053101421.
I've noticed it do this before and just thought "that was weird" but this time I figured I'd google to see if anyone else had had this problem ... and found this post.
Jul 11 2024 02:51 AM - edited Jul 11 2024 02:52 AM
Same thing happening to me for a while now. Just updated to 24152.415.2975.367 and still a problem. Client 49/24053101421.
OS Name Microsoft Windows 11 Pro
Version 10.0.22631 Build 22631
Jul 17 2024 01:59 AM
The same is happening with me, and there seems to be no logic on to which chat it switches. Have we already had any feedback to this request? @Daniele_Tesi
Jul 18 2024 12:33 AM
Jul 24 2024 12:42 PM
Aug 26 2024 05:25 AM
Aug 28 2024 09:02 AM
@Daniele_TesiI'm on that patch and the problem persists.
Sep 17 2024 09:55 AM - edited Sep 17 2024 09:55 AM
For me, it happens when I select a Reaction to someoneʼs message. Itʼll jump me to whatever chat I was in previously when I let go the mouse button. Microsoft, 𝓅𝓁ℯ𝒶𝓈ℯ 𝒻𝒾𝓍!
Sep 17 2024 03:41 PM
@kskyllingmark Yes same.
And the latest versions have not resolved.
Sep 18 2024 12:40 AM - edited Sep 18 2024 12:40 AM
Seems that also the newer versions do not solve the issue.
I personally don't have the problem anymore, but I see that many other people are still having the issue so I keep the post open. @ Microsoft please fix it, this is very frustrating!