Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Steps to Reproduce
There is a common workaround people use: a
However, this has the problem that the keyboard closes momentarily and opens again immediately.
Should both send the focus to the next text field and not dismiss the keyboard momentarily.
One problem I see with this proposal is that if the Completed event does not receive the required input, it might want to reset the field and keep the user focused on that instead of giving focus to the next entry. We might also want to jump to another entry, not necessarily the next in line, depending on UI workflow.
I don't however like seeing the keyboard open and close between focus changes on the same page when we use the Completed event. This does not happen on iOS.