[GH-ISSUE #14417] issue: Artifact iframe doesn't open for javascript code blocks only #17245

New Issue

GiteaMirror · 2026-04-19T22:57:14-05:00

GiteaMirror commented

2026-04-19 22:57:14 -05:00

Originally created by @theimpostor on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14417

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.11

Ollama Version (if applicable)

No response

Operating System

macOS Sonoma

Browser (if applicable)

136.0.7103.114

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

If the assistant response includes a Javascript code block, the artifact iframe doesn't appear automatically like it does for html code blocks. Opening the artifact panel manually shows the artifact has been populated however.

Actual Behavior

A valid javascript code block is produced however the artifact remains hidden.

Steps to Reproduce

Prompt: "Write a short snippet of javascript which adds a 'hello world' div to the body"

Response:

// Create a new <div> element
const helloDiv = document.createElement('div');

// Set its text content
helloDiv.textContent = 'hello world';

// Append it to the document body
document.body.appendChild(helloDiv);

Logs & Screenshots

src/lib/components/chat/Messages/ContentRenderer.svelte should probably check for javascript, js, and css in addition to html and svg.

Additional Information

No response

Originally created by @theimpostor on GitHub (May 27, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14417 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.11 ### Ollama Version (if applicable) _No response_ ### Operating System macOS Sonoma ### Browser (if applicable) 136.0.7103.114 ### 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 If the assistant response includes a Javascript code block, the artifact iframe doesn't appear automatically like it does for html code blocks. Opening the artifact panel manually shows the artifact has been populated however. ### Actual Behavior A valid javascript code block is produced however the artifact remains hidden. ### Steps to Reproduce Prompt: "Write a short snippet of javascript which adds a 'hello world' div to the body" Response: ```javascript // Create a new <div> element const helloDiv = document.createElement('div'); // Set its text content helloDiv.textContent = 'hello world'; // Append it to the document body document.body.appendChild(helloDiv); ``` ### Logs & Screenshots src/lib/components/chat/Messages/ContentRenderer.svelte should probably check for `javascript`, `js`, and `css` in addition to `html` and `svg`. ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-19 22:57:14 -05:00

GiteaMirror closed this issue

2026-04-19 22:57:14 -05:00

GiteaMirror referenced this issue

2026-04-20 05:22:06 -05:00

[PR #17245] [MERGED] chore: changes to bug report issue template #24370

GiteaMirror referenced this issue

2026-04-25 12:24:47 -05:00

[PR #17245] [MERGED] chore: changes to bug report issue template #40000

GiteaMirror referenced this issue

2026-04-29 22:37:38 -05:00

[PR #17245] [MERGED] chore: changes to bug report issue template #47418