Moving between transactions in the confirm screen

[alextsg]

In the old UI, users were able to move between transactions when confirming:

In the new UI, we currently render the oldest transaction and the user has to confirm/reject transactions in order. Should we implement the same UX in the new UI?

[bdresser]

So right now when you prompt a transaction, you can either confirm it in the standalone popup window, or in the popup attached to the extension bar. The behavior for stacked transactions is different in each view:

• In the standalone popup window, we show the oldest transaction first (in the order they were proposed).
• In the popup attached to the extension bar, we show the most recent transaction first.
• As @alextsg mentions above, in the Old UI you can move between the transactions using the element shown, but in the New UI you can't.

I think we should standardize in showing the transactions in the order they were proposed, which also has the security benefit of preventing dapps from proposing a new transaction at the last moment.

We should also include the ability to move between the proposed transactions, as in the old UI.

Could be something as simple as this, although @cjeria should take a look

[cjeria]

Concept for displaying unconfirmed or "stacked" transactions.

[bdresser]

@alextsg @cjeria would allowing tx confirmation in whatever order the user wants cause nonce issues?

I'm actually ok with the UX as-is, especially since it keeps tx in nonce order -- I just think we should standardize behavior as described above.

Chatted with whymarrh who informed me that nonce is set when a tx is submitted which is cool 😎

Should probably wait until after #3425

[bdresser]

this was implemented as part of batch transactions