Chat jumps, can't reach latest, unread messages
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Have a long 1:1 chat
- Receive three messages
- Open the chat
Expected behaviour
I can see the latest messages
Actual behaviour
I see the latest messages briefly, then the chat jumps/scrolls months of chat history
The browser (FF) seems really busy and doesn't allow me to scroll down. If I get there it jumps back up.
Talk app
Talk app version: (see apps admin page: /index.php/settings/apps)
Custom Signaling server configured: yes/no and version (see additional admin settings: /index.php/index.php/settings/admin/talk#signaling_server)
Custom TURN server configured: yes/no (see additional admin settings: /index.php/settings/admin/talk#turn_server)
Custom STUN server configured: yes/no (see additional admin settings: /index.php/settings/admin/talk#stun_server)
Browser
Microphone available: yes/no
Camera available: yes/no
Operating system: Windows/Ubuntu/...
Browser name: Firefox/Chrome/...
Browser version: 85/96/...
Browser log
Server configuration
Operating system: Ubuntu/RedHat/...
Web server: Apache/Nginx
Database: MySQL/Maria/SQLite/PostgreSQL
PHP version: 8.0/8.1/8.2
Nextcloud Version: (see admin page)
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your server installation folder
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Server log (data/nextcloud.log)
Insert your server log here
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 long 1:1 chat scenario in Firefox: receive three messages, open the chat, and observe the scroll jump. Review the browser console and network logs, which are not included in the report, while tracing the chat view's scrolling behavior. Done means the latest messages remain reachable and the view does not jump back into older history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100