-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Dropdown search don't work with Gboard #1389
Comments
Hi, Thanks a lot for the gifs! But, It is quite difficult for me to replicate this problem. That's why I prepared two different codesandbox links for you.
Best Regards, |
In the first link everything worked fine: Everything that was written in the text input appeared in the alert. However, when testing with the Google keyboard on the second link, the alert is not always displayed. With other keyboards it works fine, but not with the Google keyboard. |
Carefully debugging the google keyboard, it is identified that this one, unlike the other keyboards, enters the onFilterChange event but never enters the computed visibleOptions, the other keyboards first enter computed visibleOptions and then pass to onFilterChange, this is extremely serious 95% of devices have this keyboard and in all the error appears |
Hi @mertsincan a greeting, I have tried to modify the nuget package in the Dropdown.vue file but it has not been possible, however I have detected as a temporary solution to use the quasar dropdown and I started to review its behavior and you find this fragment
In primevue we have an @input event on line 24, is it possible to change this to an @change to mitigate the problem? Thanks |
This reverts commit 4f73ea8.
Hello,
the search in the dropdown component does not search and does not work correctly when using the google keyboard, many users bring this keyboard by default, the error is reproducible from any phone with updated gboard even in beta phase
[ x] bug report
PrimeVue version: 3.6.0
Browser: [Mobile Chrome | Android X.X Web Browser]
The text was updated successfully, but these errors were encountered: