We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Stopping Staking Manager Recovery page can be submitted without the Transaction Hash field getting filled out.
Ideally, the Start button should be disabled if the inputs are empty or an error should appear (without the long loading times).
Discord Username and #: the4kman#4895 ETH Wallet: 0x0De8947c2ABd59C201e5EcE142bFCd22253BFC0d
The text was updated successfully, but these errors were encountered:
thank you to have opened this issue,
this is a design choice, because if you don't fill inputs everything works normally.
We made this choice, because users are able to fill just a recover input if they needs.
Have you some idea to improve the experience?
Issue From Bug to Improvement Proposal
Sorry, something went wrong.
@alet89 I would indicate somehow that the field is optional (for example, by adding the "(optional)" suffix to the placeholder text)
No branches or pull requests
Describe the bug
The Stopping Staking Manager Recovery page can be submitted without the Transaction Hash field getting filled out.
To Reproduce
Expected behavior
Ideally, the Start button should be disabled if the inputs are empty or an error should appear (without the long loading times).
Screenshots
Web3 Scenario (please complete the following information):
Reward
Discord Username and #: the4kman#4895
ETH Wallet: 0x0De8947c2ABd59C201e5EcE142bFCd22253BFC0d
The text was updated successfully, but these errors were encountered: