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

typeaheadNoResults doesn't fire on default value #6611

Open
Et3rnal opened this issue Sep 28, 2023 · 0 comments
Open

typeaheadNoResults doesn't fire on default value #6611

Et3rnal opened this issue Sep 28, 2023 · 0 comments

Comments

@Et3rnal
Copy link

Et3rnal commented Sep 28, 2023

Simply typeaheadNoResults doesn't fire/validate the initial value until the user interacts with the typeahead

Is there a way I can change that? another event to trigger this maybe?

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

1 participant