-
Notifications
You must be signed in to change notification settings - Fork 587
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
Preventing default up/down key behavior even when no suggestions are available. #517
Comments
Sounds reasonable. Would you like to contribute a PR? |
Gladly! Let me know if any changes should be made. |
@moroshko, do you know when you'd have time to merge @ShibumiGrant's changes? I also have the same issue and the proposed changes work. |
Is the any progress in Preventing default up/down key behavior? |
This is now resolved by #768 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Default behavior for pressing the up and down keys is being
preventDefault
'ed, even in cases where the autosuggest does not need to be using special handling for them. Ininput
elements, this manifests as not being able to quickly jump to the beginning and end of an input using these keys, and intextarea
andcontenteditable
elements it prevents jumping between lines.Single-line Input Reproduction Steps: (Use the Basic example)
asdf
.Observed Behavior: The cursor does not move.
Expected Behavior: The cursor moves to be in front of the first character in the input.
Multi-line Input Reproduction Steps: (Use this codepen)
asdf
.asdf
again.Observed Behavior: The cursor does not move.
Expected Behavior: The cursor moves to the line above.
The text was updated successfully, but these errors were encountered: