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

frontend: don't disable back-button in send #2870

Closed

Conversation

NicolaLS
Copy link
Contributor

Don't disable the back button in send.tsx when a dialog/modal (QR scanner, or UTXO selection) is open. It is a UX best practice to do this when a modal is open however a) our dialog CSS creates an overlay which means nothing behind it can be clicked anyways, and b) the back button currently supports ESC which should close the modal but navigates back from the send route right now.

If we don't need the is-open state for these modals we can simplify the send component in another refactor by extracting coin control into its own sub-component (moving activeCoinControl there) and moving activeScanQR into ReceiverAddressInput.

This PR does not change anything because the back-button is not clickable because of the screen size (100%) overlay used:

height: 100%;
width: 100%;
background: transparent;
z-index: 4010;

Don't disable the back button in send.tsx when a dialog/modal (QR
scanner, or UTXO selection) is open. It is a UX best practice to do this
when a modal is open **however** a) our dialog CSS creates an overlay
which means nothing behind it can be clicked anyways, and b) the back
button currently supports ESC which should close the modal but navigates
back from the send route right now.

If we don't need the is-open state for these modals we can simplify the
send component in another refactor by extracting coin control into its
own sub-component (moving `activeCoinControl` there) and moving
`activeScanQR` into `ReceiverAddressInput`.
@NicolaLS
Copy link
Contributor Author

NicolaLS commented Sep 2, 2024

having this as a PR is a bit silly, I'll do it in #2871 and #2872

@NicolaLS NicolaLS closed this Sep 2, 2024
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.

1 participant