Advertisement
Top banner ad slot
Homepage | History
Generated 2026-05-10 04:01 UTC
release

Open WebUI Patches Chat Scroll Regression in v0.9.4

Open WebUI has released v0.9.4, fixing a bug where opening a saved chat conversation would not reliably scroll to the most recent message, instead stopping short due to a CSS rendering quirk.

GitHub Open WebUI Releases <span data-utc="2026-05-10T03:59:24+00:00">2026-05-10 03:59 UTC</span> Key: evt-715c240fa924579d28fa Confidence: strong Mode: claude

Article body

Open WebUI shipped version 0.9.4 on May 9, 2026, addressing a regression in chat scroll behavior. When a user opens a saved conversation, the interface now correctly scrolls to the bottom of the message history instead of stopping partway through.

The bug was traced to the CSS property content-visibility: auto applied to chat elements. That property causes the browser to estimate element sizes before fully rendering them, which in turn caused the initial scroll-to-bottom logic to land on an incorrect position rather than the true end of the message list.

The fix arrives just hours after v0.9.3 added a Voice Mode mute toggle with an 'M' keyboard shortcut, indicating the project is in active patch cadence following a feature release.

Why this matters

  • Users who rely on Open WebUI as their daily interface for local or self-hosted LLMs depend on reliable conversation navigation, especially in long chat threads.
  • The regression was subtle enough to avoid notice in brief testing but would frustrate users reviewing extended message histories.
  • The quick follow-up patch demonstrates ongoing maintenance of the project, which is a key trust factor for self-hosted deployment tooling.

Source note

  • The release information comes directly from the Open WebUI GitHub releases page (open-webui/open-webui). The changelog is concise but specific, providing the exact CSS property and mechanism behind the regression. The broader Open WebUI project context (local LLM web UI for OpenAI-API-compatible backends) is drawn from the repo name and established use case, not from the release note itself.

Original link

Open the monitored source