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.

Sign up for GitHub

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

Jump to bottom

Input and button order when using tab navigation #1724

Closed
sabau opened this issue Dec 10, 2018 · 5 comments
Closed

Input and button order when using tab navigation #1724

sabau opened this issue Dec 10, 2018 · 5 comments
Labels
good first issue 🙌 low priority has been discussed, will be addressed later stale ux-improvement issues that would improve the user experience

Comments

@sabau
Copy link
Contributor

sabau commented Dec 10, 2018

Description:

If you try to navigate using tabs, the order not always reflect the rendered boxes, we should keep them aligned.

ModalsProposal i.e. is mostly OK, but amount comes after the readonly denom
@sabau sabau added low priority has been discussed, will be addressed later good first issue 🙌 labels Dec 10, 2018
@faboweb faboweb added the ux-improvement issues that would improve the user experience label Dec 10, 2018
@jbibla
Copy link
Collaborator

jbibla commented Dec 10, 2018

not sure what you mean @sabau can you share a screenshot?

@faboweb
Copy link
Collaborator

faboweb commented Dec 10, 2018

@jbibla "tab navigation" is hard to show in a screenshot. It means pressing the "->"/"tab" key on your keyboard.

@jbibla
Copy link
Collaborator

jbibla commented Dec 10, 2018

ohhhhhhhh thank you i misunderstood

@sabau
Copy link
Contributor Author

sabau commented Dec 11, 2018

My bad, poor explanation

@enyan94 enyan94 mentioned this issue Dec 11, 2018
Merged
This was referenced Jan 16, 2019
Merged
Merged
Merged
Merged
Merged
This was referenced Feb 14, 2019
Closed
Merged
@faboweb faboweb mentioned this issue Apr 3, 2019
Closed
@stale
Copy link

stale bot commented Aug 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 23, 2019
@stale stale bot closed this as completed Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue 🙌 low priority has been discussed, will be addressed later stale ux-improvement issues that would improve the user experience
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sabau @faboweb @jbibla