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

Expanded editor #16643

New Issue
Closed
opened 2026-02-21 19:27:02 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:27:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Sep 2, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

The expanded editor does not use the current parent panel width, but the width the panel had when the workflow editor was first loaded.

It is also not anchored in its parent, but in a fixed position on the right:

Image

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @DavideDelbianco on GitHub (Sep 2, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. The expanded editor does not use the current parent panel width, but the width the panel had when the workflow editor was first loaded. It is also not anchored in its parent, but in a fixed position on the right: <img width="1201" height="967" alt="Image" src="https://github.com/user-attachments/assets/91ffbecf-3ab7-4380-b5ae-70e59d1fd38a" /> ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🐞 bug label 2026-02-21 19:27:02 -05:00
yindo closed this issue 2026-02-21 19:27:02 -05:00
yindo commented 2026-02-21 19:27:02 -05:00
Author
Owner
Copy Link
Copy Source

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

The expanded editor's width is set based on the parent panel's width when the workflow editor first loads, and it doesn't update if the parent panel is resized. Its position is anchored in a fixed spot on the right, rather than dynamically within its parent container. This behavior is due to how the component logic and CSS are implemented: the width is determined by a state variable and not updated on parent resize, and the anchoring uses fixed styles instead of relative positioning or dynamic anchoring approaches. There are currently no recent changes or fixes addressing this in the codebase1 .

To resolve this, you could listen for parent panel resize events and update the expanded editor's width and position accordingly. In React, this typically involves using a ref to track the parent panel's dimensions and updating the editor's state when the parent resizes. Anchoring the editor relative to its parent (using relative positioning and dynamic width) would ensure it always matches the current panel size.

If you want to implement a fix, focus on updating the expanded editor's logic in editor.tsx and its styles in editor.module.css to respond to parent width changes and anchor it within the parent container.

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 2, 2025): <!-- Answer --> The expanded editor's width is set based on the parent panel's width when the workflow editor first loads, and it doesn't update if the parent panel is resized. Its position is anchored in a fixed spot on the right, rather than dynamically within its parent container. This behavior is due to how the component logic and CSS are implemented: the width is determined by a state variable and not updated on parent resize, and the anchoring uses fixed styles instead of relative positioning or dynamic anchoring approaches. There are currently no recent changes or fixes addressing this in the codebase[^1]. To resolve this, you could listen for parent panel resize events and update the expanded editor's width and position accordingly. In React, this typically involves using a ref to track the parent panel's dimensions and updating the editor's state when the parent resizes. Anchoring the editor relative to its parent (using relative positioning and dynamic width) would ensure it always matches the current panel size. If you want to implement a fix, focus on updating the expanded editor's logic in `editor.tsx` and its styles in `editor.module.css` to respond to parent width changes and anchor it within the parent container. [^1]: [Relevant code details](https://github.com/langgenius/dify/blob/2ac8f8003f0380599e07199d4380f4718d5494bb/web/app/components/workflow/nodes/_base/components/workflow-panel/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/d384b3db-039b-4b95-ba5a-f986e1570cff?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d384b3db-039b-4b95-ba5a-f986e1570cff?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d384b3db-039b-4b95-ba5a-f986e1570cff?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d384b3db-039b-4b95-ba5a-f986e1570cff?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d384b3db-039b-4b95-ba5a-f986e1570cff?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d384b3db-039b-4b95-ba5a-f986e1570cff?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d384b3db-039b-4b95-ba5a-f986e1570cff?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/24969)
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#16643
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?