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

fix(ui): do not reset field on dropdown open #4533

Closed
wants to merge 2 commits into from

Conversation

edgarkhanzadian
Copy link
Contributor

@edgarkhanzadian edgarkhanzadian commented Nov 16, 2023

Try out this version of Leather — download extension builds.

closes #4335

dropdownResetFix.mov

@markmhendrickson it is going to show an error on the wrong address when we click on the dropdown (as we click away from the input in this case). Is it fine with us?

@fbwoolf
Copy link
Contributor

fbwoolf commented Nov 16, 2023

I intentionally implemented it this way so it would clear the address type, @markmhendrickson do we really not want the behavior here? 🤔 Why would you want a bns name in the address field and vice versa?

EDIT: I think was to avoid the validation and error seen?

@markmhendrickson
Copy link
Collaborator

The idea is that the user may enter a BNS name or address quickly then realize they need to change the type selection. The current behavior means they have to enter it a second time.

@edgarkhanzadian your video is showing the input getting cleared still so I'm a bit unsure what's being demoed per se – is this the before or after your change?

@edgarkhanzadian
Copy link
Contributor Author

@markmhendrickson based on the issue i thought it shouldn't clear the input when the user clicks on the menu dropdown. Should it also not clear when user clicks on BNS name / address?

@markmhendrickson
Copy link
Collaborator

Ah yea, that's correct – my suggestion here is to have it not clear when either selecting the dropdown or selecting one of its types. That way the value persists while changing types generally.

@pete-watters
Copy link
Contributor

Can we close this off if we won't do it for a while?

@markmhendrickson
Copy link
Collaborator

Yep we can close the PR though best to keep the issue open and in the backlog for later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prevent recipient input from clearing value when selecting type menu
5 participants