Combobox Popover is closing itself when used with async API

[iangrayhazzard]

I'm trying to make an address autocomplete component using the Google Maps "Places API". For some reason, the popover element in a combobox closes itself when making asynchronous calls to the api. Could someone take a look and tell me what I'm doing wrong? Here is a minimal reproduction: CodeSandbox

Try typing in an address like "2345 SW". You'll notice when you type the "W" in "SW" the popover closes, though it can be reopened by pressing the button. You will see that there are still results to display, so I don't understand why the popover is closing, unless it is still doing some filtering logic of it's own on top of the api.

[devongovett]

Sounds similar to #5234. Maybe try allowsEmptyCollection?

[LFDanLu]

Just chiming in, but I believe @devongovett is correct that this is the same as #5234. What I believe is happening is that it is hitting this portion of the code before the api call finishes, and since there aren't any items matching your newly modified string it believes it should close the dropdown. We'll be looking to refactor this hook to use stuff from the new Autocomplete, but I wonder if the hook could perhaps accept isLoading or something and therefore wait for that to flip from true to false before deciding to check if there area any matching items before closing the menu automatically