You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No hook (i.e. none of selected, autocomplete or cursorchange fired) if user types in exact match #33
So almost everything works: if the user types in a string that matches part of a result and completes using tab, the autocomplete event fires and the correct item is selected. If the user uses the arrow keys or the mouse to select from the dropdown, that works. Even if the user types in the whole string matching a result but in the wrong case, and then presses tab, it works. BUT if the user types in a string that precisely matches the result, no event is fired and there is no direct way that I can find to get the data from the matching Json result into the form. I think this is a bug.
I want to second this as being an issue that bites me as well. Was there a resolution? I see #34 referenced here - is it a satisfactory fix? What do the maintainers think?
Vaibhav, if you're asking me: I'm afraid I've heard nothing. But I'm happy with my patch for now. One thing, I did become aware of yet another fork, https://github.com/algolia/autocomplete.js
I agree that this would be a bug - @mallyvai have you checked out #34? If so please comment on the pull request. The maintainers are still getting up to speed, and at least I am not exactly an expert in the library.
Activity
https://github.com/corejavascript/typeahead.js/issues/33
mallyvai commentedon Nov 12, 2015
I want to second this as being an issue that bites me as well. Was there a resolution? I see #34 referenced here - is it a satisfactory fix? What do the maintainers think?
aholland commentedon Nov 12, 2015
Vaibhav, if you're asking me: I'm afraid I've heard nothing. But I'm happy with my patch for now. One thing, I did become aware of yet another fork, https://github.com/algolia/autocomplete.js
jcrben commentedon Nov 15, 2015
I agree that this would be a bug - @mallyvai have you checked out #34? If so please comment on the pull request. The maintainers are still getting up to speed, and at least I am not exactly an expert in the library.
sileence commentedon Jan 10, 2016
Having the same problem here