RocketChat / RocketChat/Rocket.Chat
The "room-opened" event is not fired in iframe under special conditions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Steps to reproduce:
In the Windows Chrome browser in Iframe Rocket Chat, if you open a chat room and go to another chat room, after returning to the previous chat, you will see that this event is not sent ("room-opened"), because maybe that page has already been loaded, if not created Please switch between the two chats several times. You can see that this event is sometimes not fired
Expected behavior:
This event is fired every time you navigate between two chat room
Server Setup Information:
Version of Rocket.Chat Server: 6.5.0
Operating System: ubuntu 22.04
Deployment Method: tar
Number of Running Instances: 1
NodeJS Version: 14.21.3
MongoDB Version: 5
Client Setup Information
Chrome Version 120.0.6099.71 (Official Build) (64-bit)
Operating System: windows 11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in a Rocket.Chat iframe using Windows Chrome by switching between two chat rooms repeatedly. Trace where the "room-opened" event is emitted during room navigation, then verify that it fires on every return to a previously opened room.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100