github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-23 18:25:10 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #21860] issue: Inconsistent HTML Rendering: Escaped in Chat, Rendered in Notification #74199

New Issue
Closed
opened 2026-05-13 06:53:23 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-13 06:53:23 -05:00
Owner
Copy Link

Originally created by @Mywk on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21860

Issue

HTML output is escaped in chat but rendered in the completion notification, resulting in inconsistent rendering behavior.

Expected Behavior

Chat messages and completion notifications should use the same rendering logic.

If HTML output is escaped in chat, it should also be escaped in the notification.
If HTML rendering is supported, it should be handled consistently in both places.

Actual Behavior

When a model outputs raw HTML (e.g. <table>...</table>):

  • In the chat view, the HTML is escaped and displayed as literal text.
  • In the completion notification, the same HTML is rendered as formatted output.

This results in inconsistent rendering between UI components.

Steps to Reproduce

  1. Start a new chat.

  2. Prompt the model to output raw HTML, for example:

    Convert this data to an HTML table and output only <table>...</table>.

  3. Observe that:

    • The chat view shows escaped HTML.
    • The completion notification renders the HTML as formatted output.

Logs & Screenshots

Image

Notes

A good model to test this with is glm-ocr.

Check Existing Issues

  • 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.8.5

Operating System

OpenSUSE Tumbleweed

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.
Originally created by @Mywk on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21860 ## Issue HTML output is escaped in chat but rendered in the completion notification, resulting in inconsistent rendering behavior. ### Expected Behavior Chat messages and completion notifications should use the same rendering logic. If HTML output is escaped in chat, it should also be escaped in the notification. If HTML rendering is supported, it should be handled consistently in both places. ### Actual Behavior When a model outputs raw HTML (e.g. `<table>...</table>`): * In the chat view, the HTML is escaped and displayed as literal text. * In the completion notification, the same HTML is rendered as formatted output. This results in inconsistent rendering between UI components. ### Steps to Reproduce 1. Start a new chat. 2. Prompt the model to output raw HTML, for example: ``` Convert this data to an HTML table and output only <table>...</table>. ``` 3. Observe that: * The chat view shows escaped HTML. * The completion notification renders the HTML as formatted output. ### Logs & Screenshots <img width="1283" height="499" alt="Image" src="https://github.com/user-attachments/assets/4e549f6f-dd42-4ae7-b240-af84d2328505" /> ### Notes A good model to test this with is glm-ocr. --- ### 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.8.5 ### Operating System OpenSUSE Tumbleweed ### 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.
GiteaMirror added the bug label 2026-05-13 06:53:23 -05:00
GiteaMirror commented 2026-05-13 06:53:25 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 1, 2026):

It's properly sanitized but notification should also match message rendering behavior, addressed in dev.

<!-- gh-comment-id:3978991868 --> @tjbck commented on GitHub (Mar 1, 2026): It's properly sanitized but notification should also match message rendering behavior, addressed in dev.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#74199
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?