Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enter key not working with typeahead #188

Open
soulflyer opened this issue Oct 8, 2018 · 2 comments
Open

enter key not working with typeahead #188

soulflyer opened this issue Oct 8, 2018 · 2 comments

Comments

@soulflyer
Copy link

soulflyer commented Oct 8, 2018

I'm trying to allow for arbitrary strings as well as suggestions from the typeahead list. It's only possible if the arbitrary string is not a substring of any of the suggestions. There is no response to an enter keypress, but tab works. If there are no possible completions, this will successfully send the arbitrary string. If there are any, it just tabs to the first possible completion and wont pass the arbritary string.

I can see this behaviour on the demo page by setting rigid? false and change-on-blur? true and trying to pass the string "he". This doesn't work, but passing the string "help-me" does as there are no further completions from that.

@soulflyer soulflyer reopened this Oct 8, 2018
@soulflyer
Copy link
Author

typeahead is now ignoring the return key completely when :rigid? is set to false and change-onblur? is tue

@kimo-k
Copy link
Contributor

kimo-k commented Nov 23, 2023

Hey, thanks for waiting 5 years for this small fix, haha.

I think I know what to do, but it's hard to be sure. Try describing the behavior in a way that's explicit, positive and comprehensive. It's hard to sort out the behavior you want from the nos, buts and implied good/bad statements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants