Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mainnet view on SH Web wallet (UX/UI) #493

Closed
Liubov-crypto opened this issue Sep 3, 2020 · 1 comment · Fixed by #495
Closed

Mainnet view on SH Web wallet (UX/UI) #493

Liubov-crypto opened this issue Sep 3, 2020 · 1 comment · Fixed by #495
Assignees

Comments

@Liubov-crypto
Copy link
Collaborator

I tried to check the transaction on my web wallet and was redirected to the mainnet directly in my wallet view.
But now, I don't know how to return to my wallet?

I logged with Web wallet and want to join Jitsi Meet via the invite link.

My steps:

  1. Click on invite Link: https://superhero.com/meet/AdequateMarriagesCorrectEqually
  2. Click on Join meeting
  3. Redirect to the Room
  4. Choose random message
  5. Click on Tip Button (Blue Diamant)
  6. Enter amount. The amount should be >0.1 ae token
  7. Click on Tip
  8. Click on Confirm on Pop up
  9. Check transaction on superhero.com feed or https://mainnet.aeternal.io/transactions/
  10. Click on "eye" on my wallet

Знімок екрана 2020-09-03 о 2 18 21 пп

I think that the user will be confused if there no option to return in the wallet. I have not seen such a button.

  • OS: Mac OS 10.13.6
  • Browser: chrome
  • Version: 85.0.4183.83

P.S. User should use Go back button on the browser to return the previous view on the wallet.

Знімок екрана 2020-09-03 о 2 38 37 пп

@mradkov
Copy link
Contributor

mradkov commented Sep 3, 2020

I cannot reproduce this on the standalone web wallet nor by using the extension or mobile app. The problem only exists in the iframed wallet on superhero.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants