github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-17 08:21:12 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[PR #24959] [CLOSED] fix: consistent conversation bubble sizes with YAML code blocks #131614

New Issue
Closed
opened 2026-05-21 17:19:09 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-21 17:19:09 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/24959
Author: @sisyphusse1-ops
Created: 5/20/2026
Status: ❌ Closed

Base: main ← Head: fix/consistent-bubble-sizes-yaml-codeblocks

📝 Commits (1)

  • 5eb4e14 fix: use min-w-0 instead of min-w-full to prevent inconsistent bubble sizes with code blocks

📊 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 — In widescreen chat bubble mode, YAML code blocks caused conversation bubbles to resize inconsistently when scrolling.

Root Cause

The message content containers used min-w-full, which forced them to be at least the full width of their parent. When code blocks (especially YAML) rendered with varying content widths, this caused the bubble to expand and contract inconsistently during scroll as elements entered/left the viewport.

Fix

Replace min-w-full with min-w-0 on the markdown-prose wrapper divs in:

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

min-w-0 is the standard fix for preventing flex/grid children from overflowing their container. It allows the content to shrink below its intrinsic minimum width, so code blocks use overflow-x: auto (already present) instead of pushing the bubble wider.

Testing

  • Verified with YAML code blocks in widescreen + chat bubble mode
  • Bubble widths remain stable while scrolling
  • No visual regression for normal text messages

🔄 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/24959 **Author:** [@sisyphusse1-ops](https://github.com/sisyphusse1-ops) **Created:** 5/20/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/consistent-bubble-sizes-yaml-codeblocks` --- ### 📝 Commits (1) - [`5eb4e14`](https://github.com/open-webui/open-webui/commit/5eb4e14e771ca5821169519f503440713d17533d) fix: use min-w-0 instead of min-w-full to prevent inconsistent bubble sizes with code blocks ### 📊 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 — In widescreen chat bubble mode, YAML code blocks caused conversation bubbles to resize inconsistently when scrolling. ## Root Cause The message content containers used `min-w-full`, which forced them to be at least the full width of their parent. When code blocks (especially YAML) rendered with varying content widths, this caused the bubble to expand and contract inconsistently during scroll as elements entered/left the viewport. ## Fix Replace `min-w-full` with `min-w-0` on the markdown-prose wrapper divs in: - `ResponseMessage.svelte` - `UserMessage.svelte` - `MultiResponseMessages.svelte` `min-w-0` is the standard fix for preventing flex/grid children from overflowing their container. It allows the content to shrink below its intrinsic minimum width, so code blocks use `overflow-x: auto` (already present) instead of pushing the bubble wider. ## Testing - Verified with YAML code blocks in widescreen + chat bubble mode - Bubble widths remain stable while scrolling - No visual regression for normal text messages --- <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-05-21 17:19:09 -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#131614
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?