[HOLD for payment 2023-10-02] Chat - IOU - Hover is not being shown after stopping to scroll

[izarutskaya]

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 a chat where there are IOU cards and scrollable conversation
2. Scroll and stop in the middle of an IOU card
3. Move the mouse horizontally on the IOU card without moving up and down to hover over other components

Expected Result:

There should be a hover indicator and context menu should show up just after stopping scrolling even if user doesn't move the mouse up and down

Actual Result:

Hover indicator and context menu doesn't show up unless user hovers over other components and comes back

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: v1.3.72-6

Reproducible in staging?: Y

Reproducible in production?: N

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

2023-09-20.17.15.27.mp4

Recording.1565.mp4

Expensify/Expensify Issue URL:

Issue reported by: @Nathan-Mulugeta

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695219522514479

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @adelekennedy (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

[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 @tylerkaraszewski (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[raymondchooi]

Proposal

Scroll while still hovering over component hides existing reaction/hover

What is the root cause of that problem?

isHoveredRef is set to false on scroll start and on scroll stop the state is set to isHoveredRef which is false

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

Remove this line:

App/src/components/Hoverable/index.js

Line 49 in d00a4d6

this.isHoveredRef = false;

The hover state is still set to false on scroll in the line below but the previous hover state can be set again if the original component is still hovered:

App/src/components/Hoverable/index.js

Line 50 in d00a4d6

this.setState({isHovered: false}, this.props.onHoverOut);

What alternative solutions did you explore?

A timeout could be applied to handle when hover state should be checked again after scroll stop

[Pluto0104]

I think this is expected behavior from this PR. Also, I can't reproduce this issue.