"Unread messages" separator appears even when chat is active or for my own messages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Hello, I noticed an issue with the "Unread messages" separator:
- The separator appears even when the chat is already open and I'm actively reading it (or even scrolling through it).
- The separator only disappears after I either send a message in that chat or the application window regains focus.
- Sometimes the separator even appears for my own messages, which is illogical because I obviously already "read" them. This also always happens if I send a message from another device.
- Every time the separator appears or disappears, the chat view jumps, which is very distracting.
Expected behavior:
- If the chat window is open and has focus, and the conversation is selected/active, the "Unread messages" separator should not appear.
- For my own messages, the separator should never be shown.
- If my own message comes after the last "unread" message, then all messages before it should automatically be considered read.
Actual behavior:
- "Unread messages" separator appears unnecessarily in the above cases.
Suggestion:
Instead of using a separator, it might be cleaner to mark unread messages directly: for example, by showing a small blue dot next to them (in place of status ticks, since those don’t exist for incoming messages). The dot would disappear when:
- the app window regains focus (with this chat selected),
- user opens chat with these unread messages,
- the scroll reaches the end of the chat.
This way the chat view remains stable, and unread messages are still clearly visible.
Diagnosis report
| Nextcloud Talk Desktop | |
|---|---|
| Version | v1.2.5 |
| Built-in Talk version | v21.1.2 |
| Release channel | stable |
| Operating system | Windows_NT 10.0.22631 (Windows 11 Pro) |
| Executable Path | C:\Users\admin\AppData\Local\NextcloudTalk\app-1.2.5\Nextcloud Talk.exe |
| Connected to | - |
| Nextcloud version | 31.0.8 |
| Nextcloud Talk version | 21.1.3 |
notifications app enabled |
✅ yes |
notify_push app enabled |
❌ no |
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
No files or tests are named in the report. Start by reproducing the separator and view-jump behavior in an active, focused chat, including messages sent from another device; done means unread markers are not shown for the active chat or the user's own messages and the chat view remains stable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100