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

User should have a way to know if claim operation on claim page was a success if they switch tabs #669

Open
Thykof opened this issue Apr 3, 2024 · 6 comments
Labels
P3 Low level priority question Further information is requested
Milestone

Comments

@Thykof
Copy link
Contributor

Thykof commented Apr 3, 2024

Problem: We need to inform the user that claim operation is a success had claimed and navigated to another browser tab

Current behavior:
user has claimable operation
user navigates to claim page
user claims
user navigates to other page
while user is not on page, the operation is success
user goes back to claim page expecting to see success but instead he sees nothing

Expected behavior:
Instead of seeing nothing, the user needs to get the information that a claim has been successful

How to do:
TBD

@Thykof Thykof added this to the Front for Mainnet milestone Apr 3, 2024
@Thykof Thykof added the P2 Mid level priority label Apr 3, 2024
@pivilartisant
Copy link
Contributor

pivilartisant commented Apr 3, 2024

"We should see the success after you change tabs and come back." => this implies a change in the flow. Right now, without changing tabs user sees the success and to get rid of success confirmation user navigates to another tab (which was the flow designed by PM). If we decide to display the success after a navigation than that would mean we need (for example) to add an "X" so the user can manually get rid of the success confirmation... which would mean that we would need to keep a copy of operations somewhere

@pivilartisant

This comment was marked as outdated.

@pivilartisant
Copy link
Contributor

pivilartisant commented Apr 3, 2024

""For the claim -> same. We should see it pending until succeeded. "" ==> this is an issue and should be fixed

But for me the two are not necessarily related and we should create two separate issues ?

@loonggamma
Copy link

@pivilartisant
for 1. Thanks for the context! I think what will solve this is to have a notification button on the History page tab - the red circle, like on connect wallets. We show it when there's a pending transaction (claim or other).
I agree with the issue though, it might cause users to panic, so the way to solve this is to tell users where to look. Is this solution possible? If not I suggest @LucasF243 to help with this UX case.

for 2. claim is not succeeded apart on the History page -> yes, we need to fix this. User should see success or error, after each pending state. We can't have it loading forever.

@pivilartisant pivilartisant changed the title Show success after switching tab User should ha Apr 4, 2024
@pivilartisant pivilartisant changed the title User should ha User should have a way to know if claim operation on claim page was a success if they switch tabs Apr 4, 2024
@pivilartisant
Copy link
Contributor

pivilartisant commented Apr 4, 2024

@pivilartisant pivilartisant added the question Further information is requested label Apr 4, 2024
@Thykof
Copy link
Contributor Author

Thykof commented Apr 4, 2024

Problem: We need to inform the user that claim operation is a success had claimed and navigated to another browser tab

Current behavior: user has claimable operation user navigates to claim page user claims user navigates to other page while user is not on page, the operation is success user goes back to claim page expecting to see success but instead he sees nothing

Expected behavior: Instead of seeing nothing, the user needs to get the information that a claim has been successful

How to do: TBD

I think this is not doable.

The scenario we would like to cover is:

  • user has claimable operation
  • user navigates to claim page
  • user claims
  • user navigates to other tab of the browser or another window of the computer
  • while user is not on page, the operation is success
  • user goes back to claim page and see the success

@pivilartisant pivilartisant added P3 Low level priority and removed P2 Mid level priority labels Apr 4, 2024
@Thykof Thykof modified the milestones: Front for Mainnet, Post V1 Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low level priority question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants