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

The "swap-in" amount input doesn't have a max length and pass to "Confirm Swap" state with exceeded balance #157

Open
Andrew718PLTS opened this issue Nov 21, 2024 · 0 comments
Assignees
Labels
automation-bug bug Something isn't working

Comments

@Andrew718PLTS
Copy link

Andrew718PLTS commented Nov 21, 2024

Description:

The "swap-in" amount input doesn't have a max length, therefore a large amount can be calculated and passed to the "Confirmation" state with a corrupted UI. We have to handle a large amounts - doesn't pass them on the first state or round and remove zeros to display it shorten.

STR:

  1. Navigate to the app
  2. Enter an exceeded amount that consist of >= 22 numbers for the swap-in amount input (e.g: 7478773923223123234925) and >= 30 numbers (e.g: 747877392322312323492566622277)
  3. Click on the "Continue" button

Actual result:

  1. The "swap-in" amount input doesn't have a max length that corrupts the UI on the "Confirm Swap" state
  2. It passes to the "Confirm Swap" state with exceeded balance with >= 22 numbers that rounds to a number with large zeros

Expected result:

  1. The "swap-in" amount input has a max length to avoid a corruption on the "Confirm Swap" state. One of the possible solution, if we want to pass it there it's to truncate it as we do on the first "Swap" state for inputs.
  2. It doesn't pass to the "Confirm Swap" state with exceeded balance

Attachments:

Screenshot 2024-11-21 at 09.39.26.png

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation-bug bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants