You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Onboarding - Keychain created and link wallet info screens - no confirmation modal on close is shown.
Onboarding is closed and user is back on Discovery page.
Keychain created screen:
Link wallet info screen:
Expected Behavior
On keychain created screen and link wallet info screen when user clicks close button, then we should show confirmation dialog with confirm and cancel buttons.
Once this dialog is set for both screens please apply it to select wallet screen as well as it has wrong content now:
Project
Frontend
What operating system are you seeing the problem on?
macOS
What browsers are you seeing the problem on?
Chrome
Relevant log output
Anything else?
Note for testers:
I added some missing tests and marked them as skipped(with this issue number tagged) until this is done. Make sure they pass and unblock them.
Please add missing tests in Onboarding suite after keychain created success step. Add checking modal content for all the steps that display it (content changes after keychain create success step so it mentions 'link wallet' being incomplete)
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
oldGreg5
changed the title
[Bug]: Onboarding - Keychain created screen - no confirmation modal on close
[Bug]: Onboarding - Keychain created and link wallet info screens - no confirmation modal on close
Mar 11, 2025
Is there an existing issue for this?
Current Behavior
Onboarding - Keychain created and link wallet info screens - no confirmation modal on close is shown.
Onboarding is closed and user is back on Discovery page.
Keychain created screen:

Link wallet info screen:

Expected Behavior
Figma design here
Project
Frontend
What operating system are you seeing the problem on?
macOS
What browsers are you seeing the problem on?
Chrome
Relevant log output
Anything else?
Note for testers:
Code of Conduct
The text was updated successfully, but these errors were encountered: