Closed will093 closed 6 years ago
@evasquez26 can you answer this question? He is expecting the opposite behaviour than your PR.
Sure :) @will093 can you explain a bit more about the case of use?
As described here https://github.com/ng2-ui/auto-complete/issues/207 what we wanted was a way to let the user write what he wants and if something matches their search then they could select it from the list, something like google does with their search, they don't automatically select the first thing that comes up, it let's you choose but also to write down whatever you want
Am also facing the issue on these. I need exactly google does.
@raviji @evasquez26 My use case is a little different from yours.
I have a form where the user picks from a list of possible options, but as there are several hundred options a simple dropdown select is not a good choice. In my use case accept-user-input
is set to false.
The idea is this:
In particular, it seems very odd with the current behaviour and accept-user-input
when the user types until there is only 1 remaining list item, hits tab, and the value reverts to what it was previously.
I think some kind of highlight-first-result
input flag might be good to at least give people that option.
Add PR #244 that permit the old behaviour.
Thank you @will093 and @lemarsu for the PR I was thinking of making this optional :)
Thanks @raviji maybe it's better better to open a new issue with that you have described because I think it's kind of different than the main issue.
@evasquez26 Thank you and sure I will open a new ticket for this.
Added PR #245 with better input name and little doc in README.md.
Current behavior
Expected/desired behavior