Forum Discussion
Drop your files here box won't go away
- Aug 23, 2022
Vivek01
I just had the same issue, my fix (for now) has been dragging an item into the chat, pressing the X on the following prompt.
I hope this helps.
With my issue, it seems to happen when you click and drag a file to a browser.
UPDATE: Someone from our tier 1 team is able to RECREATE this problem every time. She showed me and I can make my Teams chat do it. Here is how to make it happen:
-Find an image that someone posted in a chat
-VERY quickly click and drag then release... (almost like when you accidently click and drag for a millisecond)..You only want to drag a little bit so the image barely moves within its chat bubble.
-The "drop here" starts to flash and it gets caught in between.
Again, I can now reproduce this on command as can our entire organization I would suppose.
Also, pressing F1 and then going back to the chat is the fastest way to sidestep this issue for those of us in the trenches. Stay strong. 🙂
- Joshua BinesNov 23, 2022Iron Contributor
NateL1010 I'm also getting these results I assume you already have a case open with the PG about the issue?
- NateL1010Nov 23, 2022Brass Contributor
No, I don't have a support case open. If we start getting more complaints about the issue, I'll probably open a new case now that the issue can be reproduced.
- SirRealityNov 23, 2022Copper Contributor
NateL1010 - just more complaints from me? Because I'm down for that. I'm really good at it. Ask anybody who knows me. I'm wondering if the irritation factor should be measured instead of the number of people reporting the issue. I use Teams heavily for my job, as do all of my coworkers - which I believe is what Microsoft wants us to do. But having to completely exit and restart Teams mid-conversation multiple times a day creates unnecessary drag on processes that require streamlining in order to fly. That what amounts to a nit-of-a-bug to Microsoft results in a lot of itchy & scratchy on this end, and to allow a nit to make an otherwise exemplary product just about itchy enough to consider moving to a different platform, should be unacceptable to Microsoft, regardless of the number of users reporting (does Microsoft really view it as complaining?) the matter. I support back-end real estate software and am trying to imagine our telling clients that the thing that is broken in our software isn't generating enough complaints to convince us it needs fixing... even though we know it's broken since we are able to reproduce it.