-
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
Fix batch transaction UX #7473
Fix batch transaction UX #7473
Conversation
8d25d28
to
348f072
Compare
Default to showing the earliest created transaction when routing to confirm screens
348f072
to
16a085f
Compare
d9b8d53
to
b599858
Compare
b599858
to
5ed8494
Compare
await driver.wait(until.elementTextMatches(balance, /^87.*\s*ETH.*$/), 10000) | ||
await driver.wait(until.elementTextMatches(balance, /^90.*\s*ETH.*$/), 10000) | ||
const tokenAmount = await balance.getText() | ||
assert.ok(/^87.*\s*ETH.*$/.test(tokenAmount)) | ||
assert.ok(/^90.*\s*ETH.*$/.test(tokenAmount)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes are due to a send of 3 ETH now being rejected instead of approved due to the updated UI transaction order. An equivalent solution would be to ensure that transaction is approved, this was just easier.
Builds ready [5ed8494]
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -26,7 +26,7 @@ const typeHash = { | |||
|
|||
const Button = ({ type, submit, large, children, className, ...buttonProps }) => ( | |||
<button | |||
type={submit && 'submit'} | |||
type={submit ? 'submit' : undefined} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙏
* order transactions from oldest to newest in UI * update json-rpc-engine, eth-json-rpc-middleware * update e2e and integration tests
These tests were updated in #7473 to navigate in a different order, because the transaction order changed. Unfortunately this meant that a second contract deployment was being confirmed, where it was previously being rejected. This updates the test to ensure the same transaction is rejected and confirmed as prior to the change in #7473
These tests were updated in #7473 to navigate in a different order, because the transaction order changed. Unfortunately this meant that a second contract deployment was being confirmed, where it was previously being rejected. This updates the test to ensure the same transaction is rejected and confirmed as prior to the change in #7473
These tests were updated in #7473 to navigate in a different order, because the transaction order changed. Unfortunately this meant that a second contract deployment was being confirmed, where it was previously being rejected. This updates the test to ensure the same transaction is rejected and confirmed as prior to the change in #7473
These tests were updated in #7473 to navigate in a different order, because the transaction order changed. Unfortunately this meant that a second contract deployment was being confirmed, where it was previously being rejected. This updates the test to ensure the same transaction is rejected and confirmed as prior to the change in #7473
* order transactions from oldest to newest in UI * update json-rpc-engine, eth-json-rpc-middleware * update e2e and integration tests
These tests were updated in MetaMask#7473 to navigate in a different order, because the transaction order changed. Unfortunately this meant that a second contract deployment was being confirmed, where it was previously being rejected. This updates the test to ensure the same transaction is rejected and confirmed as prior to the change in MetaMask#7473
* order transactions from oldest to newest in UI * update json-rpc-engine, eth-json-rpc-middleware * update e2e and integration tests
These tests were updated in MetaMask#7473 to navigate in a different order, because the transaction order changed. Unfortunately this meant that a second contract deployment was being confirmed, where it was previously being rejected. This updates the test to ensure the same transaction is rejected and confirmed as prior to the change in MetaMask#7473
Pending
Fixes batch transaction UX by addressing long-standing errors in batch transaction handling in the UI, and modifying
json-rpc-engine
's ordered batch request handling. Transactions are now ordered from oldest to newest in the background and in the UI. Users can still freely navigate back and forth.Fixes #5852