Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4000] [FEAT]: Embedded Chat Widget – Improve data-open-on-load behavior and mobile scrolling #2543

New Issue
Open
opened 2026-02-22 18:30:08 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:30:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @Sarmingsteiner on GitHub (Jun 13, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4000

What would you like to see?

I'm using the AnythingLLM embedded chat widget and noticed two UX issues that would benefit from improvement:

  1. data-open-on-load causes automatic scroll-to-bottom on page load
    When the widget is opened via the data-open-on-load="true" option, the browser scrolls the page all the way down to the widget’s text input field. This behavior can be disruptive - especially on content-heavy pages where users are forced away from the actual page content.

Request:
Make the auto-scroll optional via a new attribute like data-scroll-to-input="true|false" (default: false), or at least disable automatic scrolling unless explicitly requested.

  1. Scrolling inside the chat widget on mobile is unreliable
    On Android and iOS, scrolling inside the widget is often difficult. It only works reliably when the user starts the gesture from the very bottom of the widget window. This leads to a frustrating UX, especially for longer conversations.

Request:
Improve touch scroll detection inside the embedded widget
Consider using touch-action CSS improvements or adjusting scroll container boundaries for more forgiving gesture handling

Environment:
Tested on latest Chrome (Android), Safari (iOS)
AnythingLLM version: latest Docker image (1.8.2)
Integration method: Embedded chat widget via <script> tag

These improvements would really enhance usability for end users and help drive adoption. Thanks for the great work on this project!

Originally created by @Sarmingsteiner on GitHub (Jun 13, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4000 ### What would you like to see? I'm using the AnythingLLM embedded chat widget and noticed two UX issues that would benefit from improvement: 1. `data-open-on-load` causes automatic scroll-to-bottom on page load When the widget is opened via the `data-open-on-load="true"` option, the browser scrolls the page all the way down to the widget’s text input field. This behavior can be disruptive - especially on content-heavy pages where users are forced away from the actual page content. **Request:** Make the auto-scroll optional via a new attribute like `data-scroll-to-input="true|false"` (default: false), or at least disable automatic scrolling unless explicitly requested. 2. Scrolling inside the chat widget on mobile is unreliable On Android and iOS, scrolling inside the widget is often difficult. It only works reliably when the user starts the gesture from the very bottom of the widget window. This leads to a frustrating UX, especially for longer conversations. **Request:** Improve touch scroll detection inside the embedded widget Consider using touch-action CSS improvements or adjusting scroll container boundaries for more forgiving gesture handling **Environment:** Tested on latest Chrome (Android), Safari (iOS) AnythingLLM version: latest Docker image (1.8.2) Integration method: Embedded chat widget via <script> tag These improvements would really enhance usability for end users and help drive adoption. Thanks for the great work on this project!
yindo added the enhancementfeature request labels 2026-02-22 18:30:08 -05:00
yindo commented 2026-02-22 18:30:09 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 13, 2025):

data-open-on-load causes automatic scroll-to-bottom on page load

This has to be a page behavior on the site the embed is placed on or how it is placed on the page (is it at the root of the document body?)
All that property does is change a state inside of the compiled JS.

Scrolling inside the chat widget on mobile is unreliable

Is there a general concensus for even rendering chat widgets like this on mobile? Real-estate is so limited on mobile it seems weird to show the widget at all, no?

@timothycarambat commented on GitHub (Jun 13, 2025): > data-open-on-load causes automatic scroll-to-bottom on page load This has to be a page behavior on the site the embed is placed on or how it is placed on the page (is it at the root of the document body?) All that property does is [change a state](https://github.com/Mintplex-Labs/anythingllm-embed/blob/4fb78337b1a85497d146de4df40460f8fb6e51a6/src/App.jsx#L17C4-L19C6) inside of the compiled JS. > Scrolling inside the chat widget on mobile is unreliable Is there a general concensus for even rendering chat widgets like this on mobile? Real-estate is so limited on mobile it seems weird to show the widget at all, no?
yindo changed title from [FEAT]: Embedded Chat Widget – Improve data-open-on-load behavior and mobile scrolling to [GH-ISSUE #4000] [FEAT]: Embedded Chat Widget – Improve data-open-on-load behavior and mobile scrolling 2026-06-05 14:47:09 -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#2543
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?