[HOLD for payment 2024-01-05] [$500] Web - Message background color is stuck on cancel delete

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Open the app
2. Open any report
3. Send any message
4. Right click on that message and click on delete comment
5. Click on cancel and now observe that irrespective on whichever message we hover, background color is stuck on message used in step 4

Expected Result:

App should remove background color from message as soon as we hover on any other message

Actual Result:

Background color on message is stuck when we right click on any message, click delete and cancel the delete

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.73.0
Reproducible in staging?: y
Reproducible in production?: y
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
Notes/Photos/Videos: Any additional supporting documentation

background.color.on.message.is.stuck.on.delete.and.cancel.mp4

Recording.4693.mp4

Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695223040847299

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~013ba33594e38dfae9
• Upwork Job ID: 1705250597563105280
• Last Price Increase: 2023-10-13
• Automatic offers:
• bernhardoj | Contributor | 28037564

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to @anmurali (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

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

[Samueljh1]

Proposal

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

The problem is that the background highlight colour on a selected message does not disappear when selecting the 'Delete Comment' popup modal and then cancelling the operation.

What is the root cause of that problem?

The issue is that the onPopoverHide() callback to handle state updates can only be called once, due to the use of the 'run and reset' paradigm. In this specific situation, this callback needs to be handled twice – once when the context menu closes, and again when the confirm delete modal changes. Since this callback is called first when the context menu closes, the subsequent cancellation of the delete modal does not call the callback to update the state of the component.

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

We allow the onPopoverHide() callback to be called several times, by not clearing the callback after the first run.

I already have a simple and elegant working solution that only requires three lines of code to be changed.

[melvin-bot]

📣 @Samueljh1! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[Samueljh1]

Contributor details
Your Expensify account email: samueljh01+test@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~01a7dc17eccbc9dc59