[Due for payment 2025-02-19] [$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link #55114

IuliiaHerets · 2025-01-11T07:58:26Z

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

Version Number: 9.0.84-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: Exp #54869
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.2
App Component: Chat Report View

Action Performed:

Go to staging.new.expensify.com
Log in with a new account.
Create a workspace.
Go to workspace chat.
Do not tap + as the tooltip should not be dismissed.
Send this link https://staging.new.expensify.com/r/6732929228344392/trip/2905990518128580779/0
Tap on the link.
Tap "Go back to home page"

Expected Result:

The educational tooltip should appear above the composer.

Actual Result:

The educational tooltip appears below the composer.

Workaround:

Unknown

Platforms:

Screenshots/Videos

Bug6711604_1736574805440.ScreenRecording_01-11-2025_13-28-55_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021878937549151677268
Upwork Job ID: 1878937549151677268
Last Price Increase: 2025-02-03

Issue Owner

Current Issue Owner: @johncschuster

melvin-bot · 2025-01-11T07:58:37Z

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

linhvovan29546 · 2025-01-11T12:49:12Z

Edited by proposal-police: This proposal was edited at 2025-01-11 12:50:26 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link

What is the root cause of that problem?

When returning from another link, the isOverlappingAtTop calculation is incorrect. This causes the function to return true, setting shouldShowBelow to true, which makes the tooltip render below the composer instead of above it.

App/src/styles/utils/generators/TooltipStyleUtils/index.ts

Line 132 in 4491e85

    
           !!(tooltip && isOverlappingAtTop(tooltip, xOffset, yOffset, tooltipTargetWidth, tooltipTargetHeight)) ||

The issue arises from the calculation based on elementAtTargetCenterX. When navigating to another link, the point at targetCenterX becomes inaccurate.

App/src/styles/utils/generators/TooltipStyleUtils/isOverlappingAtTop/index.ts

Lines 31 to 42 in 4491e85

    
           const elementAtTargetCenterX = document.elementFromPoint(targetCenterX, yOffset); 
        
           // Ensure it's not the already rendered element of this very tooltip, so the tooltip doesn't try to "avoid" itself 
        
           if (!elementAtTargetCenterX || ('contains' in tooltip && tooltip.contains(elementAtTargetCenterX))) { 
        
               return false; 
        
           } 
        
           const rectAtTargetCenterX = elementAtTargetCenterX.getBoundingClientRect(); 
        
           // Ensure it's not overlapping with another element by checking if the yOffset is greater than the top of the element 
        
           // and less than the bottom of the element. Also ensure the tooltip target is not completely inside the elementAtTargetCenterX by vertical direction 
        
           const isOverlappingAtTargetCenterX = yOffset > rectAtTargetCenterX.top && yOffset < rectAtTargetCenterX.bottom && yOffset + tooltipTargetHeight > rectAtTargetCenterX.bottom;

What changes do you think we should make in order to solve the problem?

We can easily fix this by introducing a new prop shouldForceRenderingTop, similar to the existing shouldForceRenderingBelow.

App/src/styles/utils/generators/TooltipStyleUtils/index.ts

Lines 129 to 133 in 4491e85

    
           shouldShowBelow = 
        
               shouldForceRenderingBelow || 
        
               yOffset - tooltipHeight - POINTER_HEIGHT < GUTTER_WIDTH + titleBarHeight || 
        
               !!(tooltip && isOverlappingAtTop(tooltip, xOffset, yOffset, tooltipTargetWidth, tooltipTargetHeight)) || 
        
               anchorAlignment.vertical === CONST.MODAL.ANCHOR_ORIGIN_VERTICAL.TOP;

            if (!shouldForceRenderingTop) {
                shouldShowBelow =
                    (shouldForceRenderingBelow ||
                        yOffset - tooltipHeight - POINTER_HEIGHT < GUTTER_WIDTH + titleBarHeight ||
                        !!(tooltip && isOverlappingAtTop(tooltip, xOffset, yOffset, tooltipTargetWidth, tooltipTargetHeight)) ||
                        anchorAlignment.vertical === CONST.MODAL.ANCHOR_ORIGIN_VERTICAL.TOP) && shouldForceRenderingBelow;
            }

And set shouldForceRenderingTop flag is true in here, then the tooltip will always render at the top. Since we are certain that the tooltip will not overlap at the top.

                   <EducationalTooltip
                        ...
                        shouldForceRenderingTop // new code
                    >

POC

Before	After
`Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2025-01-11.at.19.36.05.mp4`	`Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2025-01-11.at.19.21.57.mp4`

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

No, UI bug

What alternative solutions did you explore? (Optional)

After spending some time looking into the issue here, I can confirm that this proposal also resolves the issue.

bernhardoj · 2025-01-12T08:35:50Z

Proposal

Please re-state the problem that we are trying to solve in this issue.

Composer tooltip shows below the composer after going back from not found page.

What is the root cause of that problem?

When we go to the not found page, the tooltip isn't rendered. When we go back, the tooltip is rendered again and recalculates the position.

App/src/pages/home/report/ReportActionCompose/ReportActionCompose.tsx

Lines 429 to 430 in fb487a5

    
           <EducationalTooltip 
        
               shouldRender={shouldShowProductTrainingTooltip}

App/src/pages/home/report/ReportActionCompose/ReportActionCompose.tsx

Line 143 in fb487a5

shouldShowEducationalTooltip && isScreenFocused,

However, isOverlappingAtTop is true, so the tooltip is shown below the element.

App/src/styles/utils/generators/TooltipStyleUtils/index.ts

Lines 129 to 133 in fb487a5

    
           shouldShowBelow = 
        
               shouldForceRenderingBelow || 
        
               yOffset - tooltipHeight - POINTER_HEIGHT < GUTTER_WIDTH + titleBarHeight || 
        
               !!(tooltip && isOverlappingAtTop(tooltip, xOffset, yOffset, tooltipTargetWidth, tooltipTargetHeight)) || 
        
               anchorAlignment.vertical === CONST.MODAL.ANCHOR_ORIGIN_VERTICAL.TOP;

isOverlappingAtTop works by checking the element at the x-center position of the tooltip target element, that is the element that is wrapped with the tooltip, in this case the composer, and check if they are overlapping.

App/src/styles/utils/generators/TooltipStyleUtils/isOverlappingAtTop/index.ts

Lines 30 to 44 in fb487a5

    
           const targetCenterX = xOffset + tooltipTargetWidth / 2; 
        
           const elementAtTargetCenterX = document.elementFromPoint(targetCenterX, yOffset); 
        
           // Ensure it's not the already rendered element of this very tooltip, so the tooltip doesn't try to "avoid" itself 
        
           if (!elementAtTargetCenterX || ('contains' in tooltip && tooltip.contains(elementAtTargetCenterX))) { 
        
               return false; 
        
           } 
        
           const rectAtTargetCenterX = elementAtTargetCenterX.getBoundingClientRect(); 
        
           // Ensure it's not overlapping with another element by checking if the yOffset is greater than the top of the element 
        
           // and less than the bottom of the element. Also ensure the tooltip target is not completely inside the elementAtTargetCenterX by vertical direction 
        
           const isOverlappingAtTargetCenterX = yOffset > rectAtTargetCenterX.top && yOffset < rectAtTargetCenterX.bottom && yOffset + tooltipTargetHeight > rectAtTargetCenterX.bottom; 
        
           return isOverlappingAtTargetCenterX;

In our case, the overlapping element is the not found page. It's because while the page is closing, the calculation is happening.

What changes do you think we should make in order to solve the problem?

We need to wait until the page is fully closed. We can't use transitionEnd event because it's not fired. We can follow the doc by using InteractionManager.

const [isScreenTransitionEnded, setIsScreenTransitionEnded] = useState(false);

useEffect(() => {
    if (!isScreenFocused) {
        setIsScreenTransitionEnded(false);
        return;
    }
    InteractionManager.runAfterInteractions(() => {
        setIsScreenTransitionEnded(true);
    });
}, [isScreenFocused]);

Then update the shouldRender condition to only show if transition ends.

App/src/pages/home/report/ReportActionCompose/ReportActionCompose.tsx

Lines 429 to 430 in fb487a5

    
           <EducationalTooltip 
        
               shouldRender={shouldShowProductTrainingTooltip}

shouldRender={shouldShowProductTrainingTooltip && isScreenTransitionEnded}

We can create a useIsFullyFocused hook if needed.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

huult · 2025-01-13T15:49:46Z

Proposal

Please re-state the problem that we are trying to solve in this issue.

Tooltip appears below composer after returning from "Go back to home page" link

What is the root cause of that problem?

This issue occurs because we calculate the x-center position of the target before the compose box has finished rendering

App/src/styles/utils/generators/TooltipStyleUtils/isOverlappingAtTop/index.ts

Line 38 in f6c3290

const rectAtTargetCenterX = elementAtTargetCenterX.getBoundingClientRect();

App/src/pages/home/report/ReportActionCompose/ReportActionCompose.tsx

Line 440 in c7a9752

<View

For this reason, the calculated value for isOverlappingAtTop is incorrect, returning true. As a result, the condition shouldShowBelow also evaluates to true, causing this issue.

App/src/styles/utils/generators/TooltipStyleUtils/index.ts

Line 132 in 13891aa

    
           !!(tooltip && isOverlappingAtTop(tooltip, xOffset, yOffset, tooltipTargetWidth, tooltipTargetHeight)) ||

What changes do you think we should make in order to solve the problem?

This issue can occur in other cases with similar conditions. To fix this, we should update the logic to calculate isOverlappingAtTop using requestAnimationFrame to delay execution until the next render cycle, ensuring the x-center position of the target is correct.

App/src/styles/utils/generators/TooltipStyleUtils/isOverlappingAtTop/index.ts

Lines 23 to 45 in f6c3290

    
           const isOverlappingAtTop: IsOverlappingAtTop = (tooltip, xOffset, yOffset, tooltipTargetWidth, tooltipTargetHeight) => { 
        
               if (typeof document.elementFromPoint !== 'function') { 
        
                   return false; 
        
               } 
        
               // Use the x center position of the target to prevent wrong element returned by elementFromPoint 
        
               // in case the target has a border radius or is a multiline text. 
        
               const targetCenterX = xOffset + tooltipTargetWidth / 2; 
        
               const elementAtTargetCenterX = document.elementFromPoint(targetCenterX, yOffset); 
        
               // Ensure it's not the already rendered element of this very tooltip, so the tooltip doesn't try to "avoid" itself 
        
               if (!elementAtTargetCenterX || ('contains' in tooltip && tooltip.contains(elementAtTargetCenterX))) { 
        
                   return false; 
        
               } 
        
               const rectAtTargetCenterX = elementAtTargetCenterX.getBoundingClientRect(); 
        
               // Ensure it's not overlapping with another element by checking if the yOffset is greater than the top of the element 
        
               // and less than the bottom of the element. Also ensure the tooltip target is not completely inside the elementAtTargetCenterX by vertical direction 
        
               const isOverlappingAtTargetCenterX = yOffset > rectAtTargetCenterX.top && yOffset < rectAtTargetCenterX.bottom && yOffset + tooltipTargetHeight > rectAtTargetCenterX.bottom; 
        
               return isOverlappingAtTargetCenterX; 
        
           };

Update to:

  const isOverlappingAtTop: IsOverlappingAtTop = (tooltip, xOffset, yOffset, tooltipTargetWidth, tooltipTargetHeight) => {
      if (typeof document.elementFromPoint !== 'function') {
          return false;
      }

      // Use the x center position of the target to prevent wrong element returned by elementFromPoint
      // in case the target has a border radius or is a multiline text.
      const targetCenterX = xOffset + tooltipTargetWidth / 2;
      const elementAtTargetCenterX = document.elementFromPoint(targetCenterX, yOffset);

      // Ensure it's not the already rendered element of this very tooltip, so the tooltip doesn't try to "avoid" itself
      if (!elementAtTargetCenterX || ('contains' in tooltip && tooltip.contains(elementAtTargetCenterX))) {
          return false;
      }

      const rectAtTargetCenterX = elementAtTargetCenterX.getBoundingClientRect();

      let isOverlappingAtTargetCenterX = false; // add this line

      requestAnimationFrame(() => { // add this line
          isOverlappingAtTargetCenterX = yOffset > rectAtTargetCenterX.top && yOffset < rectAtTargetCenterX.bottom && yOffset + tooltipTargetHeight > rectAtTargetCenterX.bottom; // add this line
      }); // add this line

      // Ensure it's not overlapping with another element by checking if the yOffset is greater than the top of the element
      // and less than the bottom of the element. Also ensure the tooltip target is not completely inside the elementAtTargetCenterX by vertical direction

      return isOverlappingAtTargetCenterX;
  };

POC

Screen.Recording.2025-01-13.at.22.48.52.mov

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

This is a UI bug; no tests are needed.

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

melvin-bot · 2025-01-13T22:49:57Z

Job added to Upwork: https://www.upwork.com/jobs/~021878937549151677268

melvin-bot · 2025-01-13T22:50:01Z

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

melvin-bot · 2025-01-17T09:23:17Z

@johncschuster, @mollfpr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

mollfpr · 2025-01-20T11:34:01Z

The issue arises from the calculation based on elementAtTargetCenterX. When navigating to another link, the point at targetCenterX becomes inaccurate.

@linhvovan29546 What is the cause of the inaccuracy? Also, I'm not onboard yet with the workaround solution.

In our case, the overlapping element is the not found page. It's because while the page is closing, the calculation is happening.

@bernhardoj I also found the same issue on the desktop web with smallscreen when try pasting the text. Is this the same root cause?

Screen.Recording.2025-01-20.at.18.07.17.mp4

This issue occurs because we calculate the x-center position of the target before the compose box has finished rendering

@huult Same question with the issue of pasting the text.

Simulator.Screen.Recording.-.iPhone.15.17.2.-.2025-01-20.at.18.20.57.mov

linhvovan29546 · 2025-01-20T11:47:12Z

@linhvovan29546 What is the cause of the inaccuracy?

@mollfpr The RCA is the same as described here: #54925 (comment). This issue may be resolved by the selected proposal mentioned here. #54924 (comment)

mollfpr · 2025-01-20T11:56:12Z

@linhvovan29546 You're RCA mentioned that the inaccuracy happened on screen transition. How about this issue? There's no screen transition and the compose box is already rendered.

Screen.Recording.2025-01-20.at.18.07.17.mp4

linhvovan29546 · 2025-01-20T12:04:35Z

@mollfpr You can add a log here and observe that the elementAtTargetCenterX is not correct. I haven't checked the issue with pasted text, but I think it’s the same.

mollfpr · 2025-01-20T12:10:35Z

When navigating to another link, the point at targetCenterX becomes inaccurate.

@linhvovan29546 Even the elementAtTargetCenterX is not correct on the pasting text, the root is not caused because we navigate from other screen right? So, I'm not sure what the cause elementAtTargetCenterX return incorrect element.

linhvovan29546 · 2025-01-20T13:10:22Z

@mollfpr

the root is not caused because we navigate from other screen right?

Yes, my RCA is outdated

So, I'm not sure what the cause elementAtTargetCenterX return incorrect element.

The tooltip style re-render too soon, as the layout isn’t fully ready (navigation, parent layout change, etc...)

huult · 2025-01-20T15:32:18Z

@mollfpr Yes, it looks like the same RCA, and applying my solution will fix it.

Screen.Recording.2025-01-20.at.22.31.46.mov

melvin-bot · 2025-01-20T16:00:08Z

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

bernhardoj · 2025-01-21T03:47:54Z

@mollfpr it's a different RCA. For the pasting case, it overlaps with the composer content instead. It's simply because the yOffset is never updated.

App/src/styles/utils/generators/TooltipStyleUtils/isOverlappingAtTop/index.ts

Line 31 in bec182c

    
           const elementAtTargetCenterX = document.elementFromPoint(targetCenterX, yOffset);

yOffset is the y position of the composer, but it's never updated even when the composer is expanded.

a.mp4

It will be fixed by #54924

Btw, somehow I can't repro this issue anymore. (it's still overlapping with not found page, but isOverlappingAtTop is false)

melvin-bot · 2025-01-24T09:16:20Z

@johncschuster, @mollfpr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

melvin-bot · 2025-02-06T17:44:41Z

Triggered auto assignment to @grgia, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

grgia · 2025-02-06T17:54:55Z

Thanks for your proposal @bernhardoj, assigned

huult · 2025-02-06T19:44:59Z

@mollfpr could you review my feedback and my proposal?

bernhardoj · 2025-02-07T04:55:44Z

PR is ready

cc: @mollfpr

melvin-bot · 2025-02-12T22:07:34Z

Reviewing label has been removed, please complete the "BugZero Checklist".

melvin-bot · 2025-02-12T22:07:39Z

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.97-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

Fix tooltip appears below the composer when going back from another page #56513

If no regressions arise, payment will be issued on 2025-02-19. 🎊

For reference, here are some details about the assignees on this issue:

@mollfpr requires payment through NewDot Manual Requests
@bernhardoj requires payment through NewDot Manual Requests

melvin-bot · 2025-02-12T22:07:40Z

@mollfpr @johncschuster @mollfpr 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]

johncschuster · 2025-02-13T16:40:12Z

johncschuster · 2025-02-13T16:41:16Z

Payment Summary

Contributor: @bernhardoj owed $250 via NewDot
Contributor+: @mollfpr owed $250 via NewDot

bernhardoj · 2025-02-14T02:41:59Z

Requested in ND.

mollfpr · 2025-02-14T11:33:59Z

johncschuster · 2025-02-14T14:12:15Z

QA issue created. Payment summary is here! Both contributors are due payment via NewDot after the regression window has passed. Thank you!

JmillsExpensify · 2025-02-15T21:35:27Z

$250 approved for @bernhardoj

garrettmknight · 2025-02-19T10:48:43Z

$250 approved for @mollfpr

IuliiaHerets added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jan 11, 2025

melvin-bot bot assigned johncschuster Jan 11, 2025

melvin-bot bot added the Overdue label Jan 13, 2025

johncschuster added the External Added to denote the issue can be worked on by a contributor label Jan 13, 2025

melvin-bot bot changed the title ~~mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link~~ [$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link Jan 13, 2025

melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jan 13, 2025

melvin-bot bot assigned mollfpr Jan 13, 2025

melvin-bot bot removed the Overdue label Jan 13, 2025

johncschuster added this to [#whatsnext] #expense Jan 13, 2025

garrettmknight moved this to Bugs and Follow Up Issues in [#whatsnext] #expense Jan 14, 2025

melvin-bot bot added the Overdue label Jan 17, 2025

melvin-bot bot removed the Overdue label Jan 20, 2025

melvin-bot bot removed the Overdue label Feb 6, 2025

melvin-bot bot assigned grgia Feb 6, 2025

grgia assigned bernhardoj Feb 6, 2025

melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Feb 6, 2025

bernhardoj mentioned this issue Feb 7, 2025

Fix tooltip appears below the composer when going back from another page #56513

Merged

50 tasks

melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Feb 7, 2025

m-natarajan mentioned this issue Feb 12, 2025

Deploy Checklist: New Expensify 2025-02-12 #56710

Closed

33 tasks

melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Feb 12, 2025

melvin-bot bot changed the title ~~[$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link~~ [Due for payment 2025-02-19] [$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link Feb 12, 2025

melvin-bot bot removed the Reviewing Has a PR in review label Feb 12, 2025

johncschuster closed this as completed Feb 14, 2025

github-project-automation bot moved this from Bugs and Follow Up Issues to Done in [#whatsnext] #expense Feb 14, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Due for payment 2025-02-19] [$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link #55114

[Due for payment 2025-02-19] [$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link #55114

IuliiaHerets commented Jan 11, 2025 •

edited by melvin-bot bot

Loading

melvin-bot bot commented Jan 11, 2025

linhvovan29546 commented Jan 11, 2025 •

edited

Loading

bernhardoj commented Jan 12, 2025

huult commented Jan 13, 2025

melvin-bot bot commented Jan 13, 2025

melvin-bot bot commented Jan 13, 2025

melvin-bot bot commented Jan 17, 2025

mollfpr commented Jan 20, 2025

linhvovan29546 commented Jan 20, 2025

mollfpr commented Jan 20, 2025

linhvovan29546 commented Jan 20, 2025

mollfpr commented Jan 20, 2025 •

edited

Loading

linhvovan29546 commented Jan 20, 2025

huult commented Jan 20, 2025

melvin-bot bot commented Jan 20, 2025

bernhardoj commented Jan 21, 2025 •

edited

Loading

melvin-bot bot commented Jan 24, 2025

melvin-bot bot commented Feb 6, 2025

grgia commented Feb 6, 2025

huult commented Feb 6, 2025

bernhardoj commented Feb 7, 2025

melvin-bot bot commented Feb 12, 2025

melvin-bot bot commented Feb 12, 2025

melvin-bot bot commented Feb 12, 2025

johncschuster commented Feb 13, 2025

Regression Test Proposal

Precondition:

Test:

johncschuster commented Feb 13, 2025

bernhardoj commented Feb 14, 2025

mollfpr commented Feb 14, 2025

johncschuster commented Feb 14, 2025

JmillsExpensify commented Feb 15, 2025

garrettmknight commented Feb 19, 2025

[Due for payment 2025-02-19] [$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link #55114

[Due for payment 2025-02-19] [$250] mWeb - Chat - Tooltip appears below composer after returning from "Go back to home page" link #55114

Comments

IuliiaHerets commented Jan 11, 2025 • edited by melvin-bot bot Loading

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

melvin-bot bot commented Jan 11, 2025

linhvovan29546 commented Jan 11, 2025 • edited Loading

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

bernhardoj commented Jan 12, 2025

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

huult commented Jan 13, 2025

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

melvin-bot bot commented Jan 13, 2025

melvin-bot bot commented Jan 13, 2025

melvin-bot bot commented Jan 17, 2025

mollfpr commented Jan 20, 2025

linhvovan29546 commented Jan 20, 2025

mollfpr commented Jan 20, 2025

linhvovan29546 commented Jan 20, 2025

mollfpr commented Jan 20, 2025 • edited Loading

linhvovan29546 commented Jan 20, 2025

huult commented Jan 20, 2025

melvin-bot bot commented Jan 20, 2025

bernhardoj commented Jan 21, 2025 • edited Loading

melvin-bot bot commented Jan 24, 2025

melvin-bot bot commented Feb 6, 2025

grgia commented Feb 6, 2025

huult commented Feb 6, 2025

bernhardoj commented Feb 7, 2025

melvin-bot bot commented Feb 12, 2025

melvin-bot bot commented Feb 12, 2025

melvin-bot bot commented Feb 12, 2025

johncschuster commented Feb 13, 2025

BugZero Checklist:

Regression Test Proposal

Precondition:

Test:

johncschuster commented Feb 13, 2025

Payment Summary

bernhardoj commented Feb 14, 2025

mollfpr commented Feb 14, 2025

BugZero Checklist:

Regression Test Proposal

Precondition:

Test:

johncschuster commented Feb 14, 2025

JmillsExpensify commented Feb 15, 2025

garrettmknight commented Feb 19, 2025

IuliiaHerets commented Jan 11, 2025 •

edited by melvin-bot bot

Loading

linhvovan29546 commented Jan 11, 2025 •

edited

Loading

mollfpr commented Jan 20, 2025 •

edited

Loading

bernhardoj commented Jan 21, 2025 •

edited

Loading