mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
[GH-ISSUE #23990] issue: Scrolling up jumps around in a conversation/chat #35674
Reference in New Issue
Block a user
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?
Originally created by @FrameXX on GitHub (Apr 22, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23990
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.9.1
Ollama Version (if applicable)
No response
Operating System
Fedora Linux 43
Browser (if applicable)
Zen (Firefox 149.0.2)
Confirmation
README.md.Expected Behavior
I should be able to scroll without the conversation/chat jumping around.
Actual Behavior
When scrolling up in a conversation/chat it jumps back and forth usually around my queries/questions/messages.
Steps to Reproduce
Open a conversation/chat in Firefox or specifically Zen and try to scroll up. I am scrolling using a notebook touchpad. I am unable to reproduce it in a Chromium browser and this also didn't happen to me with the previous OpenWebUI version.
Logs & Screenshots
https://github.com/user-attachments/assets/31fc788c-2cc9-4bd0-b0ff-8a88b789a19b
Additional Information
These errors show in the browser console upon loading a conversation and might be relevant:
I have also noticed that while scrolling up does not jump in Chromium it seems to get bit laggy around my queries.
@DerKay3 commented on GitHub (Apr 22, 2026):
I’m experiencing the same bug.
Happens on Safari and Chrome as well.
Running Open WebUI v0.9.1.
@diminDDL commented on GitHub (Apr 22, 2026):
I am experiencing the same bug under Firefox 149.0.2 as well, it works fine when scrolling from top to bottom, but going bottom to to is full of jumps and is almost impossible to navigate.
The Firefox console also throws:
Scroll anchoring was disabled in a scroll container because of too many consecutive adjustments (12) with too little total distance (0 px average, 0 px total). ada78052-a92c-4adc-ae28-dcf46facd431and also sometimes:
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://firefox-source-docs.mozilla.org/performance/scroll-linked_effects.html for further details and to join the discussion on related tools and features! ada78052-a92c-4adc-ae28-dcf46facd431@intdel commented on GitHub (Apr 22, 2026):
Yes I have the same problem with Android Chrome 147.0
@Fade78 commented on GitHub (Apr 22, 2026):
Same problem on Firefox on Android and Linux.
@d1ffuser commented on GitHub (Apr 22, 2026):
Confirmed on Firefox and Bave.
Duplicate: https://github.com/open-webui/open-webui/discussions/23993
@mysteryx93 commented on GitHub (Apr 22, 2026):
This is definitely a regression. The major new feature is that now it creates and displays tasks with steps (and isn't even completing all the steps it displays). So this is a partially-working feature; and I'm pretty sure that's what also breaks the scrolling.
@Silvenga commented on GitHub (Apr 22, 2026):
Looks related to lazy loading/virtual dom - scrollbar jumps around too. It's almost like it's trying to remove elements from the dom within the same message (the whole message can't be displayed).
Changing the windows size mitigates it, until a different sized message is seen.
Firefox on Windows if that matters.
@Mersid commented on GitHub (Apr 22, 2026):
Confirm this happens on both Firefox and Safari (iOS). Excellent update, still!
@jxingnet commented on GitHub (Apr 23, 2026):
Same problem on chrome/egde/safari. v0.9.1.
@gmtrnv commented on GitHub (Apr 23, 2026):
Same problem in Chrome
@divemasterza commented on GitHub (Apr 23, 2026):
Same -> Chrome 147.0.7727.56 (Official Build) (arm64)
@Podden commented on GitHub (Apr 23, 2026):
Seems to be related to lazy loading the start and the end of the conversation and the different lenght of messages. Scrollbar is getting smaller and longer as well. Happens on Firefox, Chrome, Edge, WIndows, CachyOS... on mobile and PWA as well
@EuPhobos commented on GitHub (Apr 23, 2026):
Oh.. this is really annoying..
@RabiHikari commented on GitHub (Apr 23, 2026):
Same issue on my Firefox. However, my Chrome behaves a bit differently: when idle, sometimes the text glitches slightly up and down. Once scrolling, the page doesn't jump around but becomes stuttery and laggy, with the degree of lag fluctuating randomly. Seems only occur with long contexts.
@vrelk commented on GitHub (Apr 23, 2026):
Experiencing the same thing in Firefox, except it is MUCH worse than the example video when you have long messages with things like code blocks in them as it will skip entire messages.
@idealclover commented on GitHub (Apr 24, 2026):
Same here on Edge
@morbificagent commented on GitHub (Apr 24, 2026):
Yes its unuseable at the moment.
@bazzspeed commented on GitHub (Apr 24, 2026):
This is my experience:
Weird.
@D3bu9m4n commented on GitHub (Apr 24, 2026):
same issue
@tjbck commented on GitHub (Apr 24, 2026):
Addressed with the latest release.
@FrameXX commented on GitHub (Apr 24, 2026):
@tjbck
I don't think the issue went away completely. Now it only happens at the very top of a chat on first load. How to reproduce:
2 screencasts:
https://github.com/user-attachments/assets/7b82337a-3588-426a-9700-468c15f4b95d
https://github.com/user-attachments/assets/24cacd1a-bdab-46b3-8e3e-bfc511acda42
There's the issue:
Also when I open or reload a chat I get spawned in the middle of the chat. I am not sure whether that's an expected behavior.
Don't read the chat please. I am braindead.
@d1ffuser commented on GitHub (Apr 24, 2026):
@FrameXX Unable to reproduce on the latest version.
Firefox 150.0 mac.
@FrameXX commented on GitHub (Apr 24, 2026):
I tried in freshly installed Librewolf with no extensions. I am still able to reproduce it.
https://github.com/user-attachments/assets/39ff3a54-7bbd-4588-982d-40e94e990469
@TotoShampoin commented on GitHub (Apr 25, 2026):
Experiencing this too. It's incredibly annoying
@FrameXX commented on GitHub (Apr 25, 2026):
You might not actually need to scroll to the top. It's enough to just scroll to the area that isn't loaded yet.