-
Notifications
You must be signed in to change notification settings - Fork 85
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
Results disappears on keyboard dismissal on iOS #98
Comments
On IOS, if you close the keyboard, safari will automatically unfocus/blur the textbox and thus the widget will remove all suggestions. Here are some topics on stackoverflow that discuss this issue: https://stackoverflow.com/questions/27975462/prevent-blur-event-on-keyboard-close I'm not aware of any good workaround to prevent this, but if you have any suggestions, you can post them here. |
I think it would be a good idea to not remove the DOM on blur, or allow implementations to override the onBlur event which removes the content. |
Sadly this is a real deal-breaker for me. If you type |
Hi @atomtigerzoo and @NiklasBr I've developed a fix to address this issue and it should prevent the autocomplete from closing when user is closing virtual keyboard on IOS devices. Please note that this solution is a bit of a workaround, as it extends the delay before the autocomplete closes following a blur event from 200ms to 800ms. This means that if a user clicks somewhere else on a webpage, the autocomplete widget will remain visible for a longer period than before (but only on IOS devices). You can install this fix using the following command:
|
I have addressed the issue of increased delays on iOS devices. The delay should now be consistent at 200ms across different devices. Please update to the latest version by running the following command:
|
On iOS 16 searching and then dismissing the keyboard to scroll in the results will cause the results to disappear. It would be very good if they stayed
Created because #74 was incorrectly closed.
The text was updated successfully, but these errors were encountered: