RocketChat / RocketChat/Rocket.Chat

More options” (three-dots) button disappears after closing Add-on Required modal via backdrop

Open
#38,914 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug valid
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Opening an app’s More options (three-dots) menu in the Marketplace and triggering the Add-on required modal works, but dismissing the modal by clicking the backdrop causes the three-dots button to disappear from the card.
Closing the modal using the X button does not reproduce the issue.
AppMenu still renders and menu sections remain valid, but MenuV2 loses its trigger/anchor after the modal is implicitly dismissed.
This appears to be a focus-restoration / overlay lifecycle conflict between Fuselage Modal and MenuV2 rather than a marketplace state problem.

Steps to reproduce:

marketplace ---> explore ---> see cards with three dots

Expected behavior:

Closing the modal by backdrop click, ESC, or the X button should all behave the same and keep the three-dots menu visible.
Focus should return to the menu trigger so the MenuV2 anchor is preserved and the button does not disappear.

Actual behavior:
Image
Server Setup Information:
  • Version of Rocket.Chat Server:
  • License Type:
  • Number of Users:
  • Operating System:
  • Deployment Method:
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
Client Setup Information
  • Desktop App or Browser Version:
  • Operating System:
Additional context
Relevant logs:

https://github.com/user-attachments/assets/d0b03544-da34-4768-955a-2d0a38a78527

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in Marketplace > Explore on an app card, then trace the Add-on Required modal and the Fuselage Modal/MenuV2 interaction. Compare backdrop, ESC, and X dismissal, and verify that focus returns to the three-dots trigger and the menu remains visible after each path.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.