nextcloud / nextcloud/spreed

[Bug]: Chat messages are not visible until the "Join conversation" button is pressed.

Open
#12,878 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: talk-sidebar ⬅️
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

⚠️ This issue respects the following points: ⚠️
Bug description

If a comment is made on a file/image that is shared with another person there is no way for either of them to know unless they open the side bar go to the Chat tab and select the "Join conversation" button.

In the image below a comment is made on a photo that is shared with them. When refreshing the page of the source file no comment is visible until the join conversation button is pressed.

Screenshot 2024-01-21 115932

Steps to reproduce
  1. Share a file.
  2. Open shared file and make a comment.
  3. Reference original shared files Chat tab in the side panel and see that no comments are visible.
Expected behavior

when a comment is made on file it is automatically visible to everyone that has access to it. Additionally an indication that there is a comment should be easily visible on the screen even when the side panel is closed so that individuals are aware that comments have been made. Maybe a little chat bubble that when pressed pulls open the sidebar with the Chat tab selected.

Installation method

Community Docker image

Nextcloud Server version

28

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.2

Web server

Nginx

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status
No errors have been found.
Nextcloud Logs

No response

Additional info

No response

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 with the file sidebar's Chat tab and the "Join conversation" flow described in the reproduction steps; no source file or test is named. Done means comments are visible to users with access without pressing the button, with a clear indication when comments exist while the sidebar is closed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.