Skip to content
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

Autocomplete functionality should be ignored if the user presses escape #1536

Open
jbair06 opened this issue Feb 11, 2025 · 1 comment
Open
Assignees
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs
Milestone

Comments

@jbair06
Copy link
Member

jbair06 commented Feb 11, 2025

If the user is entering information into an autocomplete component and presses the 'escape' key, the component should not attempt to fill in the rest of the data.

I have an account (0.0.258xxx) which I have the key for. If I wanted to set the fee payer to be account 0.0.2, the autocomplete feature prevents me from doing this. I tried to enter 0.0.2 then press enter, or tab. Both filled in the rest of the account (0.0.258xxx) as would be expected. When I pressed escape, the popup disappeared and the field only showed 0.0.2, but then I pressed tab or enter, and the field fills in the rest (0.0.258xxx). If I click out of the field at any time, the current actual type value (0.0.2) remains as expected.

The solution would be to ensure that when 'escape' is pressed, the autocomplete does not fill in the rest of the field when tab or enter is then pressed.

@jbair06
Copy link
Member Author

jbair06 commented Feb 11, 2025

After pressing escape, the right arrow key shows the popup again, and adds the next digit as if the popup was never invisible. This is likely the expected behavior and should still remain after the solution is implemented for the described issue.

@jbair06 jbair06 added the Bug A error that causes the feature to behave differently than what was expected based on design docs label Feb 11, 2025
@jbair06 jbair06 added this to the v0.10 milestone Feb 11, 2025
@icoxxx icoxxx self-assigned this Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants