I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.6.36
Ollama Version (if applicable)
No response
Operating System
Fedora 43 & Windows 11
Browser (if applicable)
No response
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
Single ~ should not be interpreted as strikethrough.
Most of the time this issue can be observed when values are put in parentheses.
Example: (~50) (~45)
Actual Behavior
The default syntax of double ~ should be used to mark strikethrough.
Put this text inside the chat and it will be rendered incorrectly.
(~50) (~45)
Logs & Screenshots
Additional Information
No response
Originally created by @ruediger101 on GitHub (Nov 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19399
~~hi~~
~hi~
(~50) (~45)
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.36
### Ollama Version (if applicable)
_No response_
### Operating System
Fedora 43 & Windows 11
### Browser (if applicable)
_No response_
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using 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 every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
Single ~ should not be interpreted as strikethrough.
Most of the time this issue can be observed when values are put in parentheses.
Example: (~50) <sometext> (~45)
### Actual Behavior
The default syntax of double ~ should be used to mark strikethrough.
This would also be in line with this discussion https://github.com/open-webui/open-webui/discussions/11981
### Steps to Reproduce
Put this text inside the chat and it will be rendered incorrectly.
(~50) <sometext> (~45)
### Logs & Screenshots
<img width="2081" height="946" alt="Image" src="https://github.com/user-attachments/assets/b9fdb284-a56d-4e76-9bc4-547d9b17fca6" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-13 05:46:46 -05:00
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 @ruediger101 on GitHub (Nov 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19399
hihi(~50) (~45)
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.36
Ollama Version (if applicable)
No response
Operating System
Fedora 43 & Windows 11
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Single ~ should not be interpreted as strikethrough.
Most of the time this issue can be observed when values are put in parentheses.
Example: (~50) (~45)
Actual Behavior
The default syntax of double ~ should be used to mark strikethrough.
This would also be in line with this discussion https://github.com/open-webui/open-webui/discussions/11981
Steps to Reproduce
Put this text inside the chat and it will be rendered incorrectly.
(~50) (~45)
Logs & Screenshots
Additional Information
No response
@tjbck commented on GitHub (Nov 23, 2025):
Updated to match ChatGPT in dev.
b0491886bc