Resolve confusion with overlooked "Continue" button while submitting Stacking initiation form

[markmhendrickson]

We've received a report from a user that was confused why they couldn't submit the Stacking initiation form having arrived at the end, when apparently they skipped over the "Continue" button above in the "Duration" section somehow (presumably having gone back to edit it?).

We may want to modify the UX here so the individual "Continue" buttons aren't necessary for submitting the overall form, as long as all input values are provided validly.

cc @GinaAbrams

[kyranjamie]

Interesting. My read of this is that we should better communicate there's a step left to "continue".

We should keep the individual step submission though. It's friction that adds a very absolute You have selected this action.

For now, at least, I'd suggest Confirm and lock button is always enabled, but has an error when you haven't finished one particular step, which instructs the user to complete them. And perhaps change the wording from something more helpful than continue.

[markmhendrickson]

That makes me think we should lean even further into cleaning all this up by removing the section-by-section continue buttons entirely and convert the right-column confirmation module into a blocking "Confirm transaction" type screen after the user submits this form entirely with one submit button at the end.

That way the user gets one chance to review all the values they've entered in a serial way instead of having to confirm one-by-one, going back to finalize each step in case they've skipped over them.

It would also be a move in the direction of standardizing our transaction signing flows in general:

1. Form for entering data with validation upon submit
2. Confirmation screen with all entered data shown and back button to form for correction
3. Ledger or password entry screen for signing transaction
4. Pending transaction view
5. Confirmed transaction view