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

Approve button does not update #14741

Closed
nbgoku opened this issue Sep 19, 2023 · 0 comments · Fixed by #14746
Closed

Approve button does not update #14741

nbgoku opened this issue Sep 19, 2023 · 0 comments · Fixed by #14746
Assignees

Comments

@nbgoku
Copy link

nbgoku commented Sep 19, 2023

Describe the bug

On https://bridge.jolnir.taiko.xyz/

If I set the initial token to bridge to be BLL, and set the number of tokens to be 10 - the approve button becomes active and you can click it

But if I decide I want to do HORSE instead and select it from the drop down menu, the approve button remains inactive/unclickable

The only way to make that button work is if I edit the token number - which was currenlty on 10 - also I can simply just click the Backspace button my keyboard and it will activate the button

The Approve button should automatically be active/clickable after simply changing the token I want to bridge from the drop down menu, I shouldn't need to update the number of tokens to activate it

Steps to reproduce

  1. https://bridge.jolnir.taiko.xyz/
  2. Select any token you want to bridge from the drop down menu
  3. Input number of tokens to bridge
  4. Notice the Approve button is active/clickable
  5. Change the token you want to send from the drop down menu
  6. Notice the Approve button is not active/clickable - it should be active/clickable however
  7. Click the backspace button on the number of tokens to bridge or update the number
  8. Notice the Approve button is active/clickable

Additional context

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants