open-webui / open-webui/computer
bug: Markdown code blocks and lists are not converted to rendered elements when they do not appear as the first text
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I discovered that in the Open Computer chatbox, markdown elements such as code blocks and lists are not converted into the correct rendered element when they do not appear as the first text in a message, and that markdown symbols inside code (such as _ or backticks) are interpreted as markdown formatting instead of raw text.
Steps to reproduce:
- Open a new conversation in Open Computer.
- Type some text (e.g.,
abc) and press Enter to move to a new line. - Type ``` to start a code block.
- Observe that no code block element is created. Instead, the ``` is displayed as raw text inside the chatbox.
- Include markdown symbols such as
_or backticks within the code. - Observe that these symbols are interpreted as markdown formatting rather than being treated as raw text.
- Note that the same markdown elements render correctly when they appear as the first text in the message.
The attached screenshots demonstrate the issue.
Thank you for your time and for maintaining this project.
Best regards,
Joshua Krimmer
Contributor guide
No contributing guide indexed for this repository
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 with the Open Computer chatbox's markdown rendering path and reproduce the issue by placing text before a code block or list. Verify that code blocks and lists render after preceding text and that underscores and backticks inside code remain raw text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100