Docker Container Logs:
I didn't notice anything relevant in it, but here it is. docker.log
Screenshots/Screen Recordings (if applicable):
See Expected/Actual Behavior sections.
Additional Information
This seems to fix the issue: I took the Expected Behavior screenshots from a build with this fix.
I can make a merge request if that helps.
Best regards
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
Originally created by @OhMajesticLama on GitHub (Jan 21, 2025).
# Bug Report
## Installation Method
I encountered the issue with the docker version:
```ghcr.io/open-webui/open-webui main f19b0d75f82a```
I can reproduce the bug with a git clone from `https://github.com/open-webui/open-webui` and then `bash run.sh`.
## Environment
- **Open WebUI Version:** v0.5.4 and commit cc2dd0ea9563f8cdce2eeccc5791965f38f5cff7
- **Ollama (if applicable):** Not applicable
- **Operating System:** Fedora 41 and Ubuntu 24.04
- **Browser (if applicable):** Firefox 134.0.1
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on the latest version of both Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
With input:

This output:


## Actual Behavior:

## Description
**Bug Summary:**
The `<details></details>` collapsable field is not processed if there is any character between `<details>` and \n.
## Reproduction Details
**Steps to Reproduce:**
1. Enter the text in Expected Behavior/input section in a model chat box.
2. Save the message.
## Logs and Screenshots
**Browser Console Logs:**
I didn't notice anything relevant in it, but here it is.
[console-export-2025-1-21_21-1-47.txt](https://github.com/user-attachments/files/18495908/console-export-2025-1-21_21-1-47.txt)
**Docker Container Logs:**
I didn't notice anything relevant in it, but here it is.
[docker.log](https://github.com/user-attachments/files/18495969/docker.log)
**Screenshots/Screen Recordings (if applicable):**
See Expected/Actual Behavior sections.
## Additional Information
[This](https://github.com/open-webui/open-webui/commit/315d132b570d712fbaf0849acb92886e0de0515a) seems to fix the issue: I took the Expected Behavior screenshots from a build with this fix.
I can make a merge request if that helps.
Best regards
## Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @OhMajesticLama on GitHub (Jan 21, 2025).
Bug Report
Installation Method
I encountered the issue with the docker version:
ghcr.io/open-webui/open-webui main f19b0d75f82aI can reproduce the bug with a git clone from
https://github.com/open-webui/open-webuiand thenbash run.sh.Environment
Open WebUI Version: v0.5.4 and commit cc2dd0ea9563f8cdce2eeccc5791965f38f5cff7
Ollama (if applicable): Not applicable
Operating System: Fedora 41 and Ubuntu 24.04
Browser (if applicable): Firefox 134.0.1
Confirmation:
Expected Behavior:
With input:

This output:
Actual Behavior:
Description
Bug Summary:
The
<details></details>collapsable field is not processed if there is any character between<details>and \n.Reproduction Details
Steps to Reproduce:
Logs and Screenshots
Browser Console Logs:
I didn't notice anything relevant in it, but here it is.
console-export-2025-1-21_21-1-47.txt
Docker Container Logs:
I didn't notice anything relevant in it, but here it is.
docker.log
Screenshots/Screen Recordings (if applicable):
See Expected/Actual Behavior sections.
Additional Information
This seems to fix the issue: I took the Expected Behavior screenshots from a build with this fix.
I can make a merge request if that helps.
Best regards
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!