-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2024-12-05] [$250] First QAB missing tooltip for new user #51987
Comments
Triggered auto assignment to @mallenexpensify ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.First QAB missing tooltip for new user What is the root cause of that problem?This issue began after the changes in this PR. In this PR, we updated
The problem arises because when we open the FAB, What changes do you think we should make in order to solve the problem?We can change the condition so when
we can do something like this
Note: This is just pseudo code. We can achieve the same results by passing props What alternative solutions did you explore? (Optional)We can remove
|
ProposalPlease re-state the problem that we are trying to solve in this issue.The QAB toolltip doesn't show for new user. What is the root cause of that problem?This happens after #49682 where we prevent the tooltip to show in a modal. The issue that they are trying to solve is that the tooltip doesn't hide when we open a modal (or RHP).
But using that condition means that the tooltip isn't allowed to show in a modal. What changes do you think we should make in order to solve the problem?Because we want to close the tooltip when a modal will show, we need to change the logic a bit. What we should do instead is, if a modal is previously not shown, but now is visible, then close the tooltip. We can do that inside this onyx subscription.
And when we close the tooltip, we need to make sure we cancel both the timeout of show and auto close/dismiss.
That's why we need to store it on a ref so we can use it later. Then, we can remove this
Also, replaces all shouldShow with shouldRender back. |
Job added to Upwork: https://www.upwork.com/jobs/~021853953365086766977 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rayane-djouah ( |
@ishpaul777 can you provide more details plz?
Track expense or Submit expense? Thx |
Submit expense, not only scan receipt but the any of the submit flow will work |
Triggered auto assignment to @sakluger ( |
@sakluger , I'm off the next week, can you please keep an eye on this issue til I'm back? Thx |
@rayane-djouah could you please check the two proposals we got already to see if they would work? Thanks! |
Reviewing 👀 |
@Nodebrute Thank you for the proposal. However, the proposed solution will not be effective in scenarios where a tooltip is already displayed and a modal (popover) containing another tooltip is opened subsequently: Screen.Recording.2024-11-09.at.10.07.48.PM.movAlso, the tooltip will not be closed when we click on the three dots menu in saved searches: Screen.Recording.2024-11-09.at.11.15.46.PM.mov |
@bernhardoj Thank you for your proposal. I agree with your root cause analysis and the solution you've suggested. 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @pecanoro, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
PR is ready cc: @rayane-djouah |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.67-9 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 2024-12-05. 🎊 For reference, here are some details about the assignees on this issue:
|
@rayane-djouah @mallenexpensify @rayane-djouah The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
BugZero Checklist:
Regression Test Proposal
Do we agree 👍 or 👎 |
Thanks @rayane-djouah |
This seems to be not fixed on mobile screen size Screen.Recording.2024-12-09.at.10.13.41.PM.movScreen.Recording.2024-12-09.at.10.16.32.PM.mov |
@ishpaul777 This appears to be a recent regression, reproducible only on staging, and it seems unrelated to our PR, which is already in production: Screen.Recording.2024-12-09.at.7.09.36.PM.movReported on Slack: https://expensify.slack.com/archives/C049HHMV9SM/p1733768184773589 |
Resolved: #53777 (comment) |
@mallenexpensify This is ready for payment |
Contributor: @bernhardoj due $250 via NewDot Thanks! |
Requested in ND. |
$250 approved for @bernhardoj |
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: 9.0.57-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @ishpaul777
Slack conversation (hyperlinked to channel name): Expensify-bugs
Action Performed:
Sign up with new account
Open FAB, complete scan receipt flow
Open FAB again
Expected Result:
you see a QAB with tooltip
Actual Result:
you see a QAB without tooltip
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Recording.729.mp4
Expected tooltip:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mallenexpensifyThe text was updated successfully, but these errors were encountered: