Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2253] [FEAT]: Ability to scroll up and read while the response is streaming #1472

New Issue
Closed
opened 2026-02-22 18:24:58 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:24:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @MorganMarshall on GitHub (Sep 9, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2253

Originally assigned to: @shatfield4 on GitHub.

What would you like to see?

I think users would really like to be able to scroll up and read while the response is streaming.

Originally created by @MorganMarshall on GitHub (Sep 9, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2253 Originally assigned to: @shatfield4 on GitHub. ### What would you like to see? I think users would really like to be able to scroll up and read while the response is streaming.
yindo added the enhancementfeature request labels 2026-02-22 18:24:58 -05:00
yindo closed this issue 2026-02-22 18:24:58 -05:00
yindo commented 2026-02-22 18:24:59 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 9, 2024):

You can scroll when its streaming to unlock the auto-scroll down. We actually had an issue earlier this year with the streaming not following the output. So scroll up should still unlock the auto-scroll, but we will keep auto-scrolling to output streams going forward

@timothycarambat commented on GitHub (Sep 9, 2024): You can scroll when its streaming to unlock the auto-scroll down. We actually had an issue earlier this year with the streaming _not_ following the output. So scroll up should still unlock the auto-scroll, but we will keep auto-scrolling to output streams going forward
yindo commented 2026-02-22 18:24:59 -05:00
Author
Owner
Copy Link
Copy Source

@MorganMarshall commented on GitHub (Sep 9, 2024):

Oh I see. My apologies I didn't catch it. Thanks for the response

@MorganMarshall commented on GitHub (Sep 9, 2024): Oh I see. My apologies I didn't catch it. Thanks for the response
yindo commented 2026-02-22 18:24:59 -05:00
Author
Owner
Copy Link
Copy Source

@hy26v commented on GitHub (Sep 17, 2024):

This is (at least for us in the selfhosted browser version)
not working as intended.
You can disable the auto scroll, if you send the prompt while not being scrolled to the very bottom of the page.
But if you are scrolled to the bottom, which is probably the default when you write a prompt, then you can not (most of the times) "escape" the autoscroll and scolling up just pushed you down again.
Also if you are not "trapped" in the auto scroll and read a part of the answer that has already been streamed, then you sometimes scroll too far down and end up in the "scroll trap" which you can not escape.
AND the whole thing is not deterministic meaning sometimes you can scroll and escape but most of the times you can not.

@hy26v commented on GitHub (Sep 17, 2024): This is (at least for us in the selfhosted browser version) not working as intended. You can disable the auto scroll, if you send the prompt while not being scrolled to the very bottom of the page. But if you are scrolled to the bottom, which is probably the default when you write a prompt, then you can not (most of the times) "escape" the autoscroll and scolling up just pushed you down again. Also if you are not "trapped" in the auto scroll and read a part of the answer that has already been streamed, then you sometimes scroll too far down and end up in the "scroll trap" which you can not escape. AND the whole thing is not deterministic meaning sometimes you can scroll and escape but most of the times you can not.
yindo commented 2026-02-22 18:24:59 -05:00
Author
Owner
Copy Link
Copy Source

@MorganMarshall commented on GitHub (Sep 20, 2024):

2hy6v, I think this is why I've noticed it on and off, thanks

@MorganMarshall commented on GitHub (Sep 20, 2024): 2hy6v, I think this is why I've noticed it on and off, thanks
yindo commented 2026-02-22 18:24:59 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 20, 2024):

@shatfield4

@timothycarambat commented on GitHub (Sep 20, 2024): @shatfield4
yindo commented 2026-02-22 18:24:59 -05:00
Author
Owner
Copy Link
Copy Source

@justme409 commented on GitHub (Oct 9, 2024):

yeh this needs to be fixed

@justme409 commented on GitHub (Oct 9, 2024): yeh this needs to be fixed
yindo changed title from [FEAT]: Ability to scroll up and read while the response is streaming to [GH-ISSUE #2253] [FEAT]: Ability to scroll up and read while the response is streaming 2026-06-05 14:40:57 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1472
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?