If you reject transaction on the step 2, nothing happens. I assume it's not supposed to be, you need to get any info that user rejected the transaction and redirect him to index page or step 1 page.
Getting any info that you rejected the transaction and redirection to index page or step 1 page
Environment details:
OS: OS X El Capitan, 10.11.6 (15G22010)
Web Browser: Google Chrome, Version 83.0.4103.116 (Official Build) (64-bit)
Wallet: Metamask (Chrome extension), Version 8.0.3
Yeah, in general our handling of Metamask transaction rejections is nonexistent throughout the dApp. Fixing that is definitely on the radar. Thanks for reporting!
Description:
If you reject transaction on the step 2, nothing happens. I assume it's not supposed to be, you need to get any info that user rejected the transaction and redirect him to index page or step 1 page.
Steps to reproduce the behavior:
Expected behavior:
Getting any info that you rejected the transaction and redirection to index page or step 1 page
Environment details:
OS: OS X El Capitan, 10.11.6 (15G22010) Web Browser: Google Chrome, Version 83.0.4103.116 (Official Build) (64-bit)
Wallet: Metamask (Chrome extension), Version 8.0.3
Screenshots