langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Studio Load More not triggering #19972

New Issue
Closed
opened 2026-02-21 20:05:11 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:05:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @YunySun on GitHub (Oct 27, 2025).

Originally assigned to: @WTW0313 on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Studio goes to the bottom to load more without triggering

Triggered after changing the resolution and loading more

Image

Original resolution 2K, scaled 125%
Can load more. Resolution 1080P, scaled 100%

✔️ Expected Behavior

load more

❌ Actual Behavior

Studio Load More not triggering

Originally created by @YunySun on GitHub (Oct 27, 2025). Originally assigned to: @WTW0313 on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="2544" height="1261" alt="Image" src="https://github.com/user-attachments/assets/6e58ceb0-3b9d-4d77-b854-b7f519a3f84a" /> Studio goes to the bottom to load more without triggering Triggered after changing the resolution and loading more <img width="2433" height="1210" alt="Image" src="https://github.com/user-attachments/assets/a7e8f063-0139-4ba5-8bd7-b8bd3e1ef866" /> Original resolution 2K, scaled 125% Can load more. Resolution 1080P, scaled 100% ### ✔️ Expected Behavior load more ### ❌ Actual Behavior Studio Load More not triggering
yindo added the 🐞 bug label 2026-02-21 20:05:11 -05:00
yindo closed this issue 2026-02-21 20:05:11 -05:00
yindo commented 2026-02-21 20:05:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 27, 2025):

This issue with "Load More" not triggering after changing resolution or scaling is likely related to fragile frontend infinite scroll or pagination logic. The React component responsible for document list pagination manages state and updates the UI based on page and limit, but event listeners or scroll calculations may not properly re-initialize after a resolution or scaling change, causing the trigger to fail. This kind of bug has been reported before in earlier Dify versions, where adjusting browser zoom or display scaling could break or restore "Load More" behavior. Some users have worked around it by manually refreshing the page, resetting scaling, or adjusting browser zoom to force the UI to recalculate the scroll container size and trigger loading again (example, discussion).

Recent code changes have optimized pagination input handling, but there is no direct fix for resolution/scaling-related "Load More" issues yet (pagination PR). Until a more robust solution is implemented, you can try refreshing the page after changing resolution/scaling, or toggling browser zoom to see if it re-enables the trigger. If you need a more permanent fix, the frontend logic for scroll event listeners or intersection observers may need to be updated to handle dynamic viewport changes.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 27, 2025): <!-- Answer --> This issue with "Load More" not triggering after changing resolution or scaling is likely related to fragile frontend infinite scroll or pagination logic. The React component responsible for document list pagination manages state and updates the UI based on page and limit, but event listeners or scroll calculations may not properly re-initialize after a resolution or scaling change, causing the trigger to fail. This kind of bug has been reported before in earlier Dify versions, where adjusting browser zoom or display scaling could break or restore "Load More" behavior. Some users have worked around it by manually refreshing the page, resetting scaling, or adjusting browser zoom to force the UI to recalculate the scroll container size and trigger loading again ([example](https://github.com/langgenius/dify/issues/22913), [discussion](https://github.com/langgenius/dify/issues/23963)). Recent code changes have optimized pagination input handling, but there is no direct fix for resolution/scaling-related "Load More" issues yet ([pagination PR](https://github.com/langgenius/dify/pull/26481)). Until a more robust solution is implemented, you can try refreshing the page after changing resolution/scaling, or toggling browser zoom to see if it re-enables the trigger. If you need a more permanent fix, the frontend logic for scroll event listeners or intersection observers may need to be updated to handle dynamic viewport changes. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/b1e6faaa-1005-4af8-8d1b-b15e0902d062?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b1e6faaa-1005-4af8-8d1b-b15e0902d062?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b1e6faaa-1005-4af8-8d1b-b15e0902d062?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b1e6faaa-1005-4af8-8d1b-b15e0902d062?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b1e6faaa-1005-4af8-8d1b-b15e0902d062?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b1e6faaa-1005-4af8-8d1b-b15e0902d062?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b1e6faaa-1005-4af8-8d1b-b15e0902d062?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27541)
yindo commented 2026-02-21 20:05:12 -05:00
Author
Owner
Copy Link
Copy Source

@WTW0313 commented on GitHub (Oct 28, 2025):

Hello, @YunySun. Could you please provide a complete video or additional details, such as the browser you are currently using? I tried to reproduce the issue but I failed.

@WTW0313 commented on GitHub (Oct 28, 2025): Hello, @YunySun. Could you please provide a complete video or additional details, such as the browser you are currently using? I tried to reproduce the issue but I failed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
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: langgenius/dify#19972
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?