github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 08:59:13 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #15557] app/ui: chat content scrolls out of view while waiting for response #56448

New Issue
Open
opened 2026-04-29 10:50:11 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-29 10:50:11 -05:00
Owner
Copy Link

Originally created by @matteocelani on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15557

What is the issue?

When sending a message in a chat, the loading indicator (three dots) appears at the bottom. At this point, it is possible to scroll down well past the actual content, causing the entire conversation to disappear above the viewport. The user is left looking at an empty area with no way to understand what happened unless they scroll back up.

Steps to reproduce

  1. Open a chat and send a message
  2. While the loading indicator (three dots) is visible, scroll down manually
  3. The chat content moves above the viewport and becomes completely invisible

Video

https://github.com/user-attachments/assets/12f2f01b-c26f-4994-9d46-3f6cea8014e8

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

0.20.6

Originally created by @matteocelani on GitHub (Apr 13, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15557 ### What is the issue? When sending a message in a chat, the loading indicator (three dots) appears at the bottom. At this point, it is possible to scroll down well past the actual content, causing the entire conversation to disappear above the viewport. The user is left looking at an empty area with no way to understand what happened unless they scroll back up. ### Steps to reproduce 1. Open a chat and send a message 2. While the loading indicator (three dots) is visible, scroll down manually 3. The chat content moves above the viewport and becomes completely invisible ### Video https://github.com/user-attachments/assets/12f2f01b-c26f-4994-9d46-3f6cea8014e8 ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version 0.20.6
GiteaMirror added the bug label 2026-04-29 10:50:12 -05:00
GiteaMirror commented 2026-04-29 10:50:13 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15557
Analyzed: 2026-04-18T18:20:43.558630

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274307064 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15557 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15557 **Analyzed**: 2026-04-18T18:20:43.558630 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
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/ollama#56448
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?