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

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.