[HOLD for payment 2024-02-07] Context menu - Context menu opens in LHN when navigating via Tab and Enter key

[lanitochka17]

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: 1.4.27-0
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Hover over any message in chat
2. Click on the empty area inside the hover menu
3. Navigate to overflow menu via Tab
4. Hit Enter

Expected Result:

The context menu will open near the hover menu

Actual Result:

The context menu opens in LHN

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6346583_1705587656418.20240118_212922.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @slafortune

[github-actions]

👋 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.

[lanitochka17]

#vip-vsb

[esh-g]

It was known while making the PR here: #34031 (comment)
We decided not to block the deploy because of it. There is another pending PR where this should be fixed.

[mountiny]

This is known, we decided to move ahead and fix as a follow up

[esh-g]

@mountiny Would it be possible to reconsider the total bounty for this issue (including the original), since this required 2 PRs and a lot more changes than normal bugs? I would suggest the previous bounty ($1000) but I'm good with any decision you take.

[mountiny]

It required 2 Prs only because we decided this new bug can be treated as a follow up

bumping to $600 dont think more would be fair compared to other issues/ feature request

[melvin-bot]

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

[melvin-bot]

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

• Fix Overflow menu from keyboard and show left-out options only #34754

If no regressions arise, payment will be issued on 2024-02-07. 🎊

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

• @rushatgabhane requires payment through NewDot Manual Requests
• @esh-g requires payment (Needs manual offer from BZ)

[melvin-bot]

Triggered auto assignment to @slafortune (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

[mountiny]

Wait payment for this is handled here #33573 so closing