Onclick sometimes passes in text i typed in, not the value of the item I selected

[jaykav99]

Forgive me I am very unfamiliar with this library I didnt implement it. But we are trying using this during a stock item selection. I can type in the word 'tran' and I get back a list of 15 items...some I click on and it passes the value of my clicked on stock item to the rest of the code that verifies its a valid stock item.

But then some after the I select it passes on the word 'tran' instead like the onclick failed or was replaced with the selection. Can anyone think of why that may happen?

[tkirda-bison]

You need to share how you set up the plugin. Otherwise, it’s difficult to pinpoint what might be wrong.

[tkirda-bison]

Closing as not actionable in its current form, with apologies for the long silence.

The select / onSelect path has been reshaped meaningfully since this was filed (2.0.1, released today):

• fix: fire onSearchComplete before onSelect when auto-selecting #870 — onSearchComplete now fires before onSelect on a single-match auto-select.
• fix: coerce non-string suggestion values at the response boundary #871 — Suggestion.value is normalized to string at every response boundary.
• groupBy shows group name but doesn't group results #859 — groupBy now stably groups instead of duplicating headers.
• GHSA-hvqh-jw65-wcpq — default formatGroup / formatResult now escape HTML.

Without your original setup (the onSelect handler, whether preserveInput / autoSelectFirst / triggerSelectOnValidInput were customized, and whether a separate change handler was reading input.value), there isn't a clear path to reproduce "passes typed text instead of clicked item's value" against current master.

If this is still reproducible for you against 2.0.1, please open a fresh issue with:

• the autocomplete options object you initialize with,
• the onSelect callback body, and
• a short steps-to-reproduce.

I'll dig into it promptly. Thanks for the original report.

[tkirda]

Closing as not actionable in its current form, with apologies for the long silence.

The select / onSelect path has been reshaped meaningfully since this was filed (2.0.1, released today):

• fix: fire onSearchComplete before onSelect when auto-selecting #870 — onSearchComplete now fires before onSelect on a single-match auto-select.
• fix: coerce non-string suggestion values at the response boundary #871 — Suggestion.value is normalized to string at every response boundary.
• groupBy shows group name but doesn't group results #859 — groupBy now stably groups instead of duplicating headers.
• GHSA-hvqh-jw65-wcpq — default formatGroup / formatResult now escape HTML.

Without your original setup (the onSelect handler, whether preserveInput / autoSelectFirst / triggerSelectOnValidInput were customized, and whether a separate change handler was reading input.value), there isn't a clear path to reproduce "passes typed text instead of clicked item's value" against current master.

If this is still reproducible for you against 2.0.1, please open a fresh issue with:

• the autocomplete options object you initialize with,
• the onSelect callback body, and
• a short steps-to-reproduce.

I'll dig into it promptly. Thanks for the original report.