github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 02:48:13 -05:00
Code Issues 1.1k Packages Projects Releases 126 Wiki Activity

[PR #23025] [CLOSED] fix: prevent inconsistent conversation bubble sizes with YAML code bl… #26978

New Issue
Closed
opened 2026-04-20 06:47:56 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 06:47:56 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/23025
Author: @harshad-dhokane
Created: 3/25/2026
Status: ❌ Closed

Base: main ← Head: fix/inconsistent-bubble-sizes-5975

📝 Commits (1)

  • 2e81af2 fix: prevent inconsistent conversation bubble sizes with YAML code blocks (#5975)

📊 Changes

3 files changed (+3 additions, -3 deletions)

View changed files

📝 src/lib/components/chat/Messages/MultiResponseMessages.svelte (+1 -1)
📝 src/lib/components/chat/Messages/ResponseMessage.svelte (+1 -1)
📝 src/lib/components/chat/Messages/UserMessage.svelte (+1 -1)

📄 Description

Summary

Fixes #5975 — Conversation bubbles resize inconsistently when scrolling in widescreen mode with YAML code blocks.

Root Cause

The min-w-full on the markdown-prose container combined with white-space: pre-wrap on pre elements allowed code block content to push bubble widths beyond the parent's max-w-5xl constraint, causing inconsistent resizing during scroll.

Fix

Added overflow-hidden to the markdown-prose container divs in:

  • ResponseMessage.svelte
  • UserMessage.svelte
  • MultiResponseMessages.svelte

This prevents code block content from expanding the bubble width beyond the parent container's max-width constraint. The code blocks themselves already have overflow-x-auto internally for horizontal scrolling of long lines.

Testing

  • Verified the fix addresses the YAML code block scenario described in #5975
  • The overflow-hidden on the prose container is a standard CSS containment pattern that breaks the intrinsic size feedback loop without affecting normal content rendering

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/23025 **Author:** [@harshad-dhokane](https://github.com/harshad-dhokane) **Created:** 3/25/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/inconsistent-bubble-sizes-5975` --- ### 📝 Commits (1) - [`2e81af2`](https://github.com/open-webui/open-webui/commit/2e81af28a0a2804f1a84c9cea136d63effcef968) fix: prevent inconsistent conversation bubble sizes with YAML code blocks (#5975) ### 📊 Changes **3 files changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/components/chat/Messages/MultiResponseMessages.svelte` (+1 -1) 📝 `src/lib/components/chat/Messages/ResponseMessage.svelte` (+1 -1) 📝 `src/lib/components/chat/Messages/UserMessage.svelte` (+1 -1) </details> ### 📄 Description ## Summary Fixes #5975 — Conversation bubbles resize inconsistently when scrolling in widescreen mode with YAML code blocks. ## Root Cause The `min-w-full` on the markdown-prose container combined with `white-space: pre-wrap` on `pre` elements allowed code block content to push bubble widths beyond the parent's `max-w-5xl` constraint, causing inconsistent resizing during scroll. ## Fix Added `overflow-hidden` to the markdown-prose container divs in: - `ResponseMessage.svelte` - `UserMessage.svelte` - `MultiResponseMessages.svelte` This prevents code block content from expanding the bubble width beyond the parent container's max-width constraint. The code blocks themselves already have `overflow-x-auto` internally for horizontal scrolling of long lines. ## Testing - Verified the fix addresses the YAML code block scenario described in #5975 - The `overflow-hidden` on the prose container is a standard CSS containment pattern that breaks the intrinsic size feedback loop without affecting normal content rendering --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-20 06:47:56 -05:00
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 pull-request
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#26978
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?