Open myyc opened 6 years ago
For the record, this fixes it:
return <div style={{...style, ...{visibility: items.length > 10 ? "hidden" : "visible"}}} children={items} />;
It's not the same but it's probably fine. Not sure if you have a clue why the earlier version doesn't work.
I ran into this about an hour ago, and I narrowed it down to me modifying what is rendered in the div. I added pagination to my autocomplete, and I was going to render a loading spinner when the user pages. First page would render, then when I clicked the button, the component would bomb like yours did. I removed my rendering logic around the loading and just await
ed the promise to render the new page of results, and all was well.
This was a new one for me. If you find out the problem, please document it so maybe I can re-add my loading spinner.
Not really. I am still using the workaround :)
I'm also seeing this one if I change what appears in the menu after it has already, e.g to change the rendered menu from a list of items to the text Loading..
while a new search is in place.
+1
Check #287
Hi,
not sure if this is the right place to report it, I figured you'd be able to give me a hand. My
renderMenu
looks like this:as I expect to have a ton of results (typically they shrink as the user types 2-3 letters).
when I type the letter "n" (?????) the whole thing crashes on Chrome giving these error messages:
I really have no idea what the issue is... any clues?
Edit: implicitly mentioned, works fine on other browsers.
Edit 2: worth noting that this works