-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2023-12-26] [$500] Wallet - Button to confirm bank account deletion is off-screen #29729
Comments
Triggered auto assignment to @laurenreidexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.The Confirm Modal is anchored to the account row rendering parts of it offscreen. What is the root cause of that problem?We render the confirm content here:
This is anchored to the Bank Account Row. Since the bank account element is near the bottom of screen, the popover when taking it as an anchor gets rendered offscreen. What changes do you think we should make in order to solve the problem?We always show confirm actions with We should simply use the Replace: App/src/pages/settings/Wallet/WalletPage/WalletPage.js Lines 459 to 476 in c5a5244
With: <ConfirmModal
isVisible
onConfirm={() => {
deletePaymentMethod();
hideDefaultDeleteMenu();
}}
onCancel={hideDefaultDeleteMenu}
contentStyles={!isSmallScreenWidth ? [styles.sidebarPopover, styles.willChangeTransform] : undefined}
title={translate('walletPage.deleteAccount')}
prompt={translate('walletPage.deleteConfirmation')}
confirmText={translate('common.delete')}
cancelText={translate('common.cancel')}
anchorPosition={{
top: anchorPosition.anchorPositionTop,
right: anchorPosition.anchorPositionRight,
}}
shouldShowCancelButton
danger
/> It wraps the content in a Result:Screencast.from.17-10-23.10.05.44.AM.IST.webmScreencast.from.17-10-23.10.06.20.AM.IST.webmCancel Task PopoverWe will be adding a trigger to show the confirmation modal here: App/src/pages/home/HeaderView.js Line 116 in a8482e2
and carry out the action when it is confirmed from the modal. What alternative solutions did you explore? (Optional)We can refactor the |
Job added to Upwork: https://www.upwork.com/jobs/~0181bf24251c643efc |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
Judging by just how big the text is in the RHP of the attached video, I think the tester may have just been zoomed in too much. The button to confirm a bank account deletion appears where it should be for me (regular 100% zoom level). expensify-delete-bank-account-flow.movMaybe they could double check and share with us their zoom level to see if we can reproduce the bug. |
@Victor-Nyagudi Try to resize the browser in a way bottom has less spacing to show the modal. Screen.Recording.2023-10-18.at.1.43.05.AM.mov |
@Expensify/design What can we do here? |
cc @pac-guerreiro can you follow up and fix this one? We shouldn't open this up as a bug, but rather it can be fixed as a follow up to the work you are doing here. cc @grgia In terms of how to fix, I would think we just detect how close to the bottom of the viewport we are, and if we are too close, we launch the popover above the button. |
bump @pac-guerreiro or @grgia |
Suggesting to show with an overlay since we always confirm with a modal when an action is important. This would also be an inconsistency 🤔 We should show it in the middle of screen, similar to how we confirm other actions taken in the app:
Whereas, confirming popover in this flow appears in the RHN itself: Screencast.from.23-10-23.09.42.38.AM.IST.webmCreating an inconsistency. |
Before deciding how to move forward, I'm curious your thoughts on #29729 (comment) @shawnborton. I agree, it's interesting that we use a different pattern on this page. Was that intentional or should we change to use the overlay modal? |
Yeah, I would think we should make them all use the center alert modal style (which is a bottom-docked modal on mobile) |
Agree with Shawn—I think they should be consistent and use the center alert modal. |
not overdue |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@pac-guerreiro just following up here - can you take on this one? |
We are also missing a confirmation popover when we cancel a task. Considering this is an irreversible action and closes a report, we should add a confirmation here: cancel.task.webmThis line should trigger the popover, and on confirming we should carry out the |
Looks good to me |
@laurenreidexpensify Can you confirm the newly added copies are good? En
Es
|
bump @laurenreidexpensify |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.13-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-12-26. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@jasperhuangg, @laurenreidexpensify, @neonbhai, @Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Payment Summary: Contributor: @neonbhai $500 payment issued in Upwork Remaining Steps to Close: @Santhosh-Sellavel to complete checklist |
Not overdue Melv |
@jasperhuangg, @laurenreidexpensify, @neonbhai, @Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@jasperhuangg, @laurenreidexpensify, @neonbhai, @Santhosh-Sellavel Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
We can skip the checklist as it ended up as UI Polish i.e became an improvement eliminating rare bug as well., as we unified confirm actions on this page with center alert modal style following this #29729 (comment) |
Thanks @Santhosh-Sellavel! Does that mean we're good to close this out? Payment has been issued. |
Requested on ND |
$500 payment approved for @Santhosh-Sellavel based on this comment. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.3.85-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Pre-requisite: user must be logged in and must have added a BA to the wallet
Expected Result:
Button to confirm back account deletion should be on-screen, allowing the user to click on it
Actual Result:
Button to confirm back account deletion is off-screen, so the user cannot click on it
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Bug6239802_1697496693646.bandicam_2023-10-16_17-38-16-495.mp4
MacOS: Desktop
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Santhosh-SellavelThe text was updated successfully, but these errors were encountered: