Closed Fang- closed 6 years ago
@galenwp This interaction pattern is a remnant from the fact that the confirmation used to be that footer modal. I tend to agree with @Fang- that we should just go back to the state screen (with the ship list), unless there's a UX reason I'm not thinking of.
Yep, he's right. I had this thought but somehow was not picky enough to have you switch it.
Is there any reason the user needs to get their computed transaction off the page for backup?
If the transaction got sent to the node successfully, then no, not really. If the transaction didn't get sent properly then we don't want to navigate away anyway.
Yeah, the only thing they'll possibly need is the transaction hash, which is in the "Success" modal. Will navigate back to "State" on dismiss.
On Sat, Dec 16, 2017 at 4:29 AM, Fang notifications@github.com wrote:
If the transaction got sent to the node successfully, then no, not really. If the transaction didn't get sent properly then we don't want to navigate away anyway.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/urbit/etherwallet/issues/8#issuecomment-352180562, or mute the thread https://github.com/notifications/unsubscribe-auth/ABiQ4zKGFpQN-mQtgDglZ-lpSDBX6b8Pks5tA7fGgaJpZM4REFh7 .
After clicking "dismiss" on a transaction confirmation, I still have to click "back" in the window with the form fields I filled out. Do we return to that intentionally? We may want to return to the layer above it (ie, the place where users can select another action to do and/or view new state) instead.