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
[iOS] QSelect doesn't trigger the keyboard when using Autocomplet on more than 2 chars #14644
Comments
Hi @Bosphoramus! 👋 It looks like you provided an invalid or unsupported reproduction URL. Without a proper reproduction, your issue will have to get closed. Thank you for your collaboration. 👏 |
BTW, for me on iOS all examples with filtering do not show the keyboard (both safari and chrome) |
Same error |
Same - Autofocus doesn't work on iOS. It also doesn't work on the popup in dialog option. |
The problem still persists. When I activate Q-select with use-input the menu opens, but the input field is not selected and thus the keyboard not shown. This happens only in iOS, not on my desktop. |
Same error, in the case when q-input has autofocus, then keyboard covers q-input if the text field is below the height of the keyboard |
I don't really know what I'm doing, but this bug is blocking the release of my app so I've started to dig into it some. From what I can gather:
My question at the moment is... what's the point of the PS: I don't think this bug needs the "bug/0-needs-info" label... it repoduces in the built-in test project) |
Problem still exists. Any solution? Commenting out the call to addFocusWaitFlag in use-portal.js does not help and might have side-effects. |
What happened?
This bug was fixed in Quasar v1 but its broken again in Quasar v2, more info here, on the latest comments:
#6491
What did you expect to happen?
This bug was fixed in Quasar v1 but its broken again in Quasar v2, more info here, on the latest comments:
#6491
Reproduction URL
https://codepen.io
How to reproduce?
This bug was fixed in Quasar v1 but its broken again in Quasar v2, more info here, on the latest comments:
#6491
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Components (quasar)
Platforms/Browsers
No response
Quasar info output
No response
Relevant log output
No response
Additional context
This bug was fixed in Quasar v1 but its broken again in Quasar v2, more info here, on the latest comments:
#6491
The text was updated successfully, but these errors were encountered: