[Transaction Cancellation] Design

[fernandomg]

Implement designs based on feedback from #403

[fernandomg]

@lukasschor, this is an ongoing work.

As purposed in #403, the intention is to display the actions in a tabular form.

After some back and forth, we couldn't find a better approach to use the 'linked-list' that the current tx detail shows, so we decided to rethink the whole votes section.

Having a tabular distribution with a row per user, with its possible actions (accept or cancel), and the last column to display extra information (as the 'executor' status).

The [Execute] button should appear in a latter row, under each action column, whenever it's possible.

You can see some wireframes here: https://wireframepro.mockflow.com/view/gsmultisig#/page/D44803dacf80a77d81dbf044743fe7ea7

[lukasschor]

Did you also explore options going into this direction?

[alongoni]

Thanks @lukasschor. The second option looks great. We can test the different states of the app.

[alongoni]

@lukasschor do you prefer to keep the Confirm and Reject button down below?

Or can we continue with the current location near each user / wallet? Perhaps this option is clearer.

[lukasschor]

Yes confirm can be up there and keep the cancel button below.

[alongoni]

Hi @lukasschor!
Here can you see two flows:

1. Reject (with 1 confirmation petition)
   

2. Confirmation (whit 1 reject tx petition)
   

@fernandomg

[lukasschor]

1. Seeing this I would actually take back my vote for having reject at the bottom and have it also up there. Similar to how the confirm button is displayed
2. I would not call the button "Confirm Reject", this seems very confusing to me
3. There is a use-case to collect all confrmations and then execute later. However, for rejections I don't see this and would just force-execute with the last confirmation collected. What do you think?
4. I would just call the buttons "Confirm" & "Reject" instead of "Confirm tx" & "Reject tx"

[fernandomg]

3. There is a use-case to collect all confrmations and then execute later. However, for rejections I don't see this and would just force-execute with the last confirmation collected. What do you think?

@lukasschor, So we should slightly modify the Approve Transaction modal for that particular case, isn't it?

• No checkbox for execution
• and leave only the first sentence of the red message: Approving this transaction executes it right away.

[alongoni]

@lukasschor. We agrupated the two buttons (Confirm and Reject) near the user wallet.

This is other case, when a user confirm first and then have two options: Execute or Reject

@fernandomg

[lukasschor]

Looks great!