Combobox input issue starting from v9.2.0 and missing changelog

[joonass-visma]

When we upgrade from v9.0.13 to v9.2.0, the search behavior of our Combobox breaks so that when you try to type, the text disappears. We have used the cursor jump workaround to get around issue that cursor jumps to end when trying to type in the middle of the input text. Removing this workaround fixes the search issue but then we get the cursor jump issue, and it seems that cursor jump issue is never going to be fixed / is unfixable from Downshift's point of view.

So would be really nice to see from somewhere what has happened between those 2 versions that causes this. I could use the compare feature in releases pages but with 128 files changed between the versions and not knowing the codebase makes it kinda hard to try to pinpoint what causes this.

[silviuaavram]

Hey @joonass-visma could you provide a repro environment so we could check the broken behavior? Thanks!

[joonass-visma]

@silviuaavram Thanks for the quick reply. Here is codesandbox: https://codesandbox.io/p/sandbox/downshift-bug-fxxnfw. Use-case is a bit unique as we are trying to use combobox as regular text field while also being searchable select.

Steps to reproduce: simply try to type to the input field and text disappears instantly. If you remove the onChange workaround for the input cursor jump, then it starts working, but that is not an option for us. While doing the sandbox I noticed that for some reason onSelectedItemChange gets called with selectedItem: null item which seems to be the reason it starts going wrong. But I don't understand why downshift does this.

[silviuaavram]

Thanks @joonass-visma I will take a look!