-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Upward Scrolling to Load More Messages in Chat Component #11848
Comments
Hi, @Woo0ood. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. Issue Summary:
Next Steps:
Thank you for your understanding and contribution! |
Before the era of Terminator or The Matrix arrives, I’d like to sincerely thank @dosubot, who, unfortunately, couldn’t join the team in person for some vacation fun or drinks (after all, he’s not an entity yet and can’t interact with us hand-in-hand🍻), but still diligently handled my issue. I’ve read and understood your response. At the same time, I hope the Dify team will have time to review my PR(#12348) once you’re back from vacation🏂. And perhaps consider rewarding DosuBot for his hard work—maybe an RTX 4090, or even a quantum processor with an unlimited power supply. After all, even AI Bots🤖 might need a little reward during this holiday season. Thanks again, and I wish the Dify team a fantastic vacation🍾, while my PR(#12348) gets the recognition he deserves! |
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Currently, the Chat component can only display the most recent 40 messages, which limits users from viewing earlier messages. To enhance user experience, we need to implement an upward scrolling feature that allows users to load more historical messages when they scroll to the top of the chat window. This will enable users to access and review older conversations seamlessly.
2. Additional context or comments
(We have fixed this or these issues and are ready to submit the PR.)
3. Can you help us with this feature?
The text was updated successfully, but these errors were encountered: