Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

ux: confusing behaviour of bridgechain transaction modals #1745

Closed
dated opened this issue Mar 1, 2020 · 3 comments
Closed

ux: confusing behaviour of bridgechain transaction modals #1745

dated opened this issue Mar 1, 2020 · 3 comments
Labels
Type: Bug The issue relates to broken or incorrect behaviour.

Comments

@dated
Copy link
Contributor

dated commented Mar 1, 2020

image

When updating / resigning a bridgechain, the respective transaction modal is added on top of the first modal showing the bridgechain registration details. When closing this second modal, either by hitting escape, clicking outside of it, or by using the close button, both modals are closed. This is rather poor ux and should be changed to either of the following options:

  1. if there is no intention to let the user go back to the first modal, it should be closed right away when the second modal is shown
  2. if there is indeed the intention to let the user "go back", then the close event should be catched and handled accordingly to only close the second modal
@ghost
Copy link

ghost commented Mar 1, 2020

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

@stale
Copy link

stale bot commented Mar 31, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale The pull request is in need of updates but there has not been a sufficient response. label Mar 31, 2020
@alexbarnsley alexbarnsley added the Type: Bug The issue relates to broken or incorrect behaviour. label Mar 31, 2020
@stale stale bot removed the Status: Stale The pull request is in need of updates but there has not been a sufficient response. label Mar 31, 2020
@faustbrian
Copy link
Contributor

Closing, no longer relevant for 3.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Bug The issue relates to broken or incorrect behaviour.
Projects
None yet
Development

No branches or pull requests

3 participants