-
-
Notifications
You must be signed in to change notification settings - Fork 852
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
Allow Persistent Results #705
Conversation
- Results from the search can be made to persist after the blur event has been fired and focus from the input is lost.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add keepResultsAfterBlur: false
to the default props.
Thanks for the PR! |
No problem at all - i'm just glad my first PR experience was a nice one so thank you too! |
Useful and I think it reduces the autocomplete billing per request !! waiting for release!! @bell-steven @haydncomley |
This was completed and merged into master - should be available to use right now as long as you've pulled the last version I believe. |
It hasn't been release on npm yet, I am waiting for another commit before releasing. |
Sorry for the delay in getting this out. |
Results from the search can be made to persist after the blur event has been fired and focus from the input is lost.
This is helpful in a variety of situations where the on screen keyboard needs to be hidden or focus pulled elsewhere with the results from the search still visible.