nextcloud / nextcloud/spreed

Sidebar preview is not rendering markdown

Open
#12,400 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: chat 💬 feature: frontend 🖌️
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
17h 55m
Merged PRs (30d)
350

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

  1. use markdown on last message
  2. See unrendered markdown in sidebar preview
Expected behaviour

Either markdown characters should be ignored (good luck with that regex) and not displayed or markdown should be rendered in the room preview

Actual behaviour

Unrendered markdown is shown:

image

Talk app

Talk app version: c.nc
**Custom Signaling server configured:**c.nc

Custom TURN server configured: c.nc

Custom STUN server configured: c.nc

Browser

Microphone available: yes

Camera available: yes

Operating system: Ubuntu

Browser name: Firefox

Browser version: 125

Browser log
``` Insert your browser log here, this could for example include: a) The javascript console log b) The network log c) ... ```

Server configuration

Operating system: c.nc

Web server: c.nc

Database: c.nc

PHP version: c.nc

Nextcloud Version: c.nc

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

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 by reproducing the issue in a Talk room using markdown in the last message, then trace the sidebar preview rendering entry point in the JavaScript code. No file or test is named in the issue; done means the sidebar preview no longer shows raw markdown and a regression check covers the expected rendering or omission of markdown characters.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.