RocketChat / RocketChat/Rocket.Chat
Unexpected change in appearance with Livechat popout widget (?mode=popout) when navigating to another page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
When using the popout option (such a valuable feature!) for Livechat, i.e. https://hibbitts.rocket.chat/livechat?mode=popout, the appearance of the widget unexpectedly changes when you navigate to another page
Steps to reproduce:
- Embed Livechat widget using the popout option (i.e. https://hibbitts.rocket.chat/livechat?mode=popout)
- View page with embedded Livechat widget
- Navigate to another page (and you will see the unexpected visual change in the widget, that is shadow border and close button)
Expected behavior:
I would expect no change from this initial appearance:

Actual behavior:
But this is the appearance once you have clicked on a page link to view another site page:

Server Setup Information:
- Version of Rocket.Chat Server: 3.11.1
- Operating System: cloud.rocket.chat
- Deployment Method:
- Number of Running Instances:
- DB Replicaset Oplog:
- NodeJS Version: v12.18.4
- MongoDB Version: 4.2.8 / wiredTiger (oplog Enabled)
Client Setup Information
- Desktop App or Browser Version: 3.0.3
- Operating System: Mac
Additional context
Relevant logs:
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
Start by reproducing the behavior at the Livechat popout entry point, https://hibbitts.rocket.chat/livechat?mode=popout, then navigate between pages as described. Compare the initial and post-navigation appearance, and consider the issue complete when the widget keeps the same appearance without the unexpected shadow border or close button.
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
- 45/100