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

Invite modal email input area cannot scroll when multiple emails are added #16615

New Issue
Closed
opened 2026-02-21 19:26:55 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:26:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @Saber-youMianJing on GitHub (Sep 1, 2025).

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.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Environment
Dify Version: 1.7.1
Deployment: Cloud, Self Hosted (Docker)

Steps to Reproduce
Navigate to Workspace Settings → Members
Click "Invite Team Member" button
Add multiple email addresses (15+ emails) to the input field
Observe that the input area reaches its height limit

✔️ Expected Behavior

Email input area should show a scrollbar when content exceeds the container height
Users should be able to scroll through the list of added emails
The counter line should remain visible at the bottom

Image

❌ Actual Behavior

Email input area does not scroll when content exceeds the fixed height
Users cannot view or manage emails that are outside the visible area
The entire input container appears to be non-scrollable

Image
Originally created by @Saber-youMianJing on GitHub (Sep 1, 2025). ### 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.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Environment Dify Version: 1.7.1 Deployment: Cloud, Self Hosted (Docker) Steps to Reproduce Navigate to Workspace Settings → Members Click "Invite Team Member" button Add multiple email addresses (15+ emails) to the input field Observe that the input area reaches its height limit ### ✔️ Expected Behavior Email input area should show a scrollbar when content exceeds the container height Users should be able to scroll through the list of added emails The counter line should remain visible at the bottom <img width="213" height="209" alt="Image" src="https://github.com/user-attachments/assets/6f0ff4f0-6b25-4cef-a811-9393bccbc94d" /> ### ❌ Actual Behavior Email input area does not scroll when content exceeds the fixed height Users cannot view or manage emails that are outside the visible area The entire input container appears to be non-scrollable <img width="203" height="209" alt="Image" src="https://github.com/user-attachments/assets/812e50df-fcc4-41d2-8715-3dd8c046fd73" />
yindo added the 🐞 buggood first issue labels 2026-02-21 19:26:55 -05:00
yindo closed this issue 2026-02-21 19:26:55 -05:00
yindo commented 2026-02-21 19:26:55 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 1, 2025):

It seems duplicated with https://github.com/langgenius/dify/issues/24898 ?

@crazywoola commented on GitHub (Sep 1, 2025): It seems duplicated with https://github.com/langgenius/dify/issues/24898 ?
yindo commented 2026-02-21 19:26:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 1, 2025):

This is a UI bug caused by missing or overridden scroll settings. The email input area in the Invite modal uses a tag/chip input inside a container with a fixed height, but the container does not have overflow-y: auto or a similar property set, so it doesn't scroll when there are many emails. To fix this, add a CSS rule to the container holding the email tags (or the input area itself) like:

max-height: 9rem; /* or your preferred height */
overflow-y: auto;

This will allow the input area to scroll when the content exceeds its height, letting users view and manage all added emails. Make sure no parent container has overflow: hidden that could block scrolling. The counter line should remain outside the scrollable area, so use a flex or grid layout if needed to keep it visible at the bottom.
You can see the relevant code structure and where to apply these changes here and here.

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 (Sep 1, 2025): <!-- Answer --> This is a UI bug caused by missing or overridden scroll settings. The email input area in the Invite modal uses a tag/chip input inside a container with a fixed height, but the container does not have `overflow-y: auto` or a similar property set, so it doesn't scroll when there are many emails. To fix this, add a CSS rule to the container holding the email tags (or the input area itself) like: ```css max-height: 9rem; /* or your preferred height */ overflow-y: auto; ``` This will allow the input area to scroll when the content exceeds its height, letting users view and manage all added emails. Make sure no parent container has `overflow: hidden` that could block scrolling. The counter line should remain outside the scrollable area, so use a flex or grid layout if needed to keep it visible at the bottom. You can see the relevant code structure and where to apply these changes [here](https://github.com/langgenius/dify/blob/bd482eb8eff3ab44b2d6449d637e6cf6b834b6ad/web/app/components/header/account-setting/members-page/invite-modal/index.tsx) and [here](https://github.com/langgenius/dify/blob/bd482eb8eff3ab44b2d6449d637e6cf6b834b6ad/web/app/components/base/tag-input/index.tsx). <!-- 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/f1806229-3855-4441-9716-ece3a302a197?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f1806229-3855-4441-9716-ece3a302a197?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f1806229-3855-4441-9716-ece3a302a197?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f1806229-3855-4441-9716-ece3a302a197?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f1806229-3855-4441-9716-ece3a302a197?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f1806229-3855-4441-9716-ece3a302a197?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f1806229-3855-4441-9716-ece3a302a197?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/24904)
yindo commented 2026-02-21 19:26:55 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 1, 2025):

@Saber-youMianJing Please do not open duplicated issues.

@crazywoola commented on GitHub (Sep 1, 2025): @Saber-youMianJing Please do not open duplicated issues.
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 good first issue 🐞 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#16615
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?