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

[PR #28142] fix: update input field width for retry configuration in RetryOnPanel #31958

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

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

State: closed
Merged: Yes

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

FIxes: #28141

Summary

In the UI for entering re-execution intervals (e.g., LLM blocks), the unit label is “ミリ秒” (milliseconds) in the Japanese locale. When the input field is narrow and the value grows to four digits (e.g., 1000), the unit overlaps the number, reducing readability. We’d like to widen the input field to eliminate this overlap.

Screenshots

Before
スクリーンショット 2025-11-13 0 21 04

After
スクリーンショット 2025-11-13 0 17 49

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/28142 **State:** closed **Merged:** Yes --- > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 1. Ensure there is an associated issue and you have been assigned to it > 1. Use the correct syntax to link this PR: `Fixes #<issue number>`. FIxes: #28141 ## Summary In the UI for entering re-execution intervals (e.g., LLM blocks), the unit label is “ミリ秒” (milliseconds) in the Japanese locale. When the input field is narrow and the value grows to four digits (e.g., 1000), the unit overlaps the number, reducing readability. We’d like to widen the input field to eliminate this overlap. ## Screenshots Before <img width="639" height="121" alt="スクリーンショット 2025-11-13 0 21 04" src="https://github.com/user-attachments/assets/897daf03-e02a-49ee-9eef-5068cfb10475" /> After <img width="596" height="142" alt="スクリーンショット 2025-11-13 0 17 49" src="https://github.com/user-attachments/assets/ff47425b-0333-4d53-91a2-49c6960e798a" /> ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:50:28 -05:00
yindo closed this issue 2026-02-21 20:50:28 -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#31958
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?