-
Notifications
You must be signed in to change notification settings - Fork 5k
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
"Reprice" TX UI Feedback #3885
Comments
makes sense, i agree |
understood, but caveats: for tokens we show the number of tokens we are sending, not value of tokens in usd (not always clear), and fees are paid in eth and we dont show the fee in token value (they dont pay any tokens to perform the tx) i think (too ideally?) that the user cares about "their action" (e.g. sending ex) and less about the fee |
@kumavis the last point is interesting. I wonder if we could throw it to users and ask what they think, or test/observe it without asking. |
I agree with @alacrity26. Will be conducting user tests very soon. |
If a retry/reprice/speed up tx is rejected, what's the reason behind showing the rejected event in the TX history? I believe the rejected event isn't important enough to show in the history (other tx events are more important like displaying incoming transactions). I would compare it to opening up a new text file and closing it without ever saving it. I don't need to see somewhere that I've thrown something away. I consider login and sign requests generated by a smart contract to be important to display in the tx history, but not user generated tx's.
Also some UI feedback on the "reprice" screen. I think we can reduce the overall height of data fields which would give us more vertical area to display the total cost of transaction (tx + gas price). Also wondering if we just show the total value up at the top since it's the most important piece of data @kumavis?
The text was updated successfully, but these errors were encountered: