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

[PR #8437] fix: Improve scrolling behavior for Conversation Opener #26050

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

Original Pull Request: https://github.com/langgenius/dify/pull/8437

State: closed
Merged: Yes

Checklist:

Important

Please review the checklist below before submitting your pull request.

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

Description

fix: Improve scrolling behavior for Conversation Opener

  • Before: Always scrolled to the bottom when accessing a conversation. Consequently, when users created a new conversation with a long Conversation Opener, the chat list would automatically scroll to the bottom, forcing users to scroll back up to read the Conversation Opener.
  • After: Only scroll to the bottom if the conversation has more than one message.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
**Original Pull Request:** https://github.com/langgenius/dify/pull/8437 **State:** closed **Merged:** Yes --- # Checklist: > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods # Description fix: Improve scrolling behavior for Conversation Opener - Before: Always scrolled to the bottom when accessing a conversation. Consequently, when users created a new conversation with a long Conversation Opener, the chat list would automatically scroll to the bottom, forcing users to scroll back up to read the Conversation Opener. - After: Only scroll to the bottom if the conversation has more than one message. ## Type of Change - [x] Bug fix (non-breaking change which fixes an issue)
yindo added the pull-request label 2026-02-21 20:33:55 -05:00
yindo closed this issue 2026-02-21 20:33:56 -05:00
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 pull-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: langgenius/dify#26050
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?