The message /report item should remain highlighted when context menu is being opened.

[kavimuru]

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 on web.
2. Open any report/chat.
3. Hover over any message.
4. Notice the highlighted background of the message.
5. Right click to open the context menu.

Expected result:

The message/report item background should remain highlighted when context is being opened.

Actual result:

The background flickers between highlighted and normal state when context is opened.

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web
• Desktop App

Version Number: v1.2.33-2
Reproducible in staging?: y
Reproducible in production?: n
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

screen-2022-11-28_20.20.58.mp4

Recording.1022.mp4

Expensify/Expensify Issue URL:
Issue reported by: @parasharrajat
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1669647312018439

View all open jobs on GitHub

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @arosiclair (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[thesahindia]

It's also on production. Not a blocker.

[arosiclair]

Yep reproduced both in staging v1.2.33-2 and prod v1.2.32-2. Closing

[parasharrajat]

I agree it is not deployblocker but I do not get the reason for closing this. Because it is present on PROD, we are not fixing it. 😕

[parasharrajat]

@arosiclair Bump.

[arosiclair]

Yep good point I closed this by accident. Let's mark this as a regular bug, not a blocker