-
Goal: I want the dropdown menu to close out and stay closed out such that when I click outside of the dropdown menu it's not selecting items on it.
-
Steps: I'm not sure how to constantly reproduce it, but it does show up from time to time possibly with larger dropdown list data. See the video below. The dropdown is actually open and selectable even though it's closed visibly.
Hi @tiffany, I think this is related to a bug I submitted through Retool's Support Portal a few months back.
(I know you cannot see the Portal ticket, but it's #75994204228056 for any Retool support looking on!)
Difficult to say if it's the same issue, but from your description it sure sounds like what we've been experiencing for a long while, but never 100% reproducible.
One of the last updates to my portal ticket was:
I've submitted a bug report to our engineering team and set an alert to keep you posted with any updates. No ETA yet on the fix but I'll let you know as soon as I hear more.
But that was a couple months ago, and we still experience the issue.
Hi @tiffany, thanks for getting in touch and sorry you're having this issue. We are currently actively working to resolve this particular problem. As a point of clarification, it looks like you are on a Windows system, is that correct?
...also, if you're familiar with Chrome Devtools or equivalent, you can open the Element Inspector to see if the invisible dropdown is still present on the page where you're attempting to click.
I was able to capture that there's an unmounting
div element on the page, meaning that likely something is not being cleaned up in component world.
I have videos of this too, but unfortunately with too much sensitive business info to upload in the forums.
Thanks for getting back to us! And thanks @dguzzo for filing the issue and sharing more about what you know. It's been bugging my users and me for probably almost a year now. I've noticed it happening a lot less lately but still occasionally (I am on mac), but my users (on Windows) are still experiencing it regularly.
Thanks for the additional info Tiffany and again sorry you have been experiencing this problem!
bugging my users and me for probably almost a year now
yep, i just checked and our first internal rumbling of this was in Nov '23! It's certainly a squirrelly one, which is why it took us so long to report to Retool.
Glad it's being looked at more closely now and we're similarly eager for a resolution.
Hi everyone - thank you for your comments and feedback! I just wanted to post an update here that we've issued a fix for this which should be live on 3.96.0!