-
Notifications
You must be signed in to change notification settings - Fork 1
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
Bug in the patient name field #52
Comments
@laurasstephan I need more technical info about the browser version or at least the phone model and Android version |
Phone is SM-G920I and Android version 7.0 |
Found this: vuejs/vue#9777 And it's a very concerning problem. I tried a lot and I couldn't figure a fix out. @kuroski, would you take a look at this? I think I've exhausted my frontend skills in trying to fix it. |
It shall impact a huge amount of users, so it's a high priority. |
Unfortunately, I think there is nothing much we can do right now, this is a problem that happens with some Android devices because of the google keyboard. There are more issues regarding this problem: And there is a PR in the Vue repository to fix that: I've tried to use the suggestions from people on the issue and nothing worked:
What happens is:
=/ I'll continue trying to fix that, but I don't think we will have much to do. |
Finally, I think I've got it =DDD First I've tried a different approach: https://github.com/kuroski/v-eager But then I checked again, and we don't have this problem on other screens that have forms. Actually the problem was really simple. We were setting the form variables as Please check the closing commit for more details |
I am testing as a patient in an old Android default browser ("Samsung internet"?).
In the Name field, it only allows me to proceed when I type a name (let's say "Teste") + space. If I do not add the space, it erases whatever I had typed and asks me for the Name again.
I've recorded a video of the bug, but it was too big to add here - ask me on Whatsapp.
The text was updated successfully, but these errors were encountered: