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

The Workflow Studio page exhibits cable jitter when hovering on a 4K screen, but works normally on 1080P. #21437

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

Originally created by @yiyouguisu on GitHub (Jan 5, 2026).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

Image

❌ Actual Behavior

No response

Originally created by @yiyouguisu on GitHub (Jan 5, 2026). ### 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.11.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="4198" height="1388" alt="Image" src="https://github.com/user-attachments/assets/96362fa2-b216-44e0-b403-91523b89c00e" /> ### ✔️ Expected Behavior <img width="1373" height="627" alt="Image" src="https://github.com/user-attachments/assets/5a512ff6-9d8c-45a9-8717-1eada8463561" /> ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:12:33 -05:00
yindo closed this issue 2026-02-21 20:12:33 -05:00
yindo commented 2026-02-21 20:12:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 5, 2026):

Hi @yiyouguisu! I'm Dosu and I’m helping the dify team.

The cable jitter on 4K screens is caused by how the Workflow Studio renders connector lines using SVG paths with floating-point coordinates, without any high-DPI-specific adjustments or coordinate rounding. This makes the cables visually unstable at high resolutions, while they appear stable at 1080P. There are no CSS properties like shape-rendering or will-change applied to the SVG elements, and no devicePixelRatio or scaling logic in the code to address this issue.

Performance and jitter get much worse if browser hardware acceleration is disabled, because the browser creates extra compositing layers—especially if the parent of the workflow container uses the border-t class with overflow: hidden. Removing the border-t class from the parent div of the workflow container can dramatically improve performance and reduce jitter on 4K screens, increasing FPS and reducing composite layers from 10+ to just 1. This has been confirmed by community testing and browser dev tools profiling [source].

There are no built-in configuration flags or official workarounds in Dify for this issue. For now, you can try removing the border-t class from the parent of the workflow container and ensure hardware acceleration is enabled in your browser. For a code-level fix, consider experimenting with adding shape-rendering="geometricPrecision" or will-change="transform" to the SVG path elements in CustomEdge and CustomConnectionLine, or rounding coordinates before passing them to getBezierPath, though these changes would require frontend code edits [source].

If you need more detailed steps for any of these suggestions, let me know!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 5, 2026): <!-- Greeting --> Hi @yiyouguisu! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The cable jitter on 4K screens is caused by how the Workflow Studio renders connector lines using SVG paths with floating-point coordinates, without any high-DPI-specific adjustments or coordinate rounding. This makes the cables visually unstable at high resolutions, while they appear stable at 1080P. There are no CSS properties like shape-rendering or will-change applied to the SVG elements, and no devicePixelRatio or scaling logic in the code to address this issue. Performance and jitter get much worse if browser hardware acceleration is disabled, because the browser creates extra compositing layers—especially if the parent of the workflow container uses the border-t class with overflow: hidden. Removing the border-t class from the parent div of the workflow container can dramatically improve performance and reduce jitter on 4K screens, increasing FPS and reducing composite layers from 10+ to just 1. This has been confirmed by community testing and browser dev tools profiling [[source](https://github.com/langgenius/dify/issues/29153#issuecomment-3612918701)]. There are no built-in configuration flags or official workarounds in Dify for this issue. For now, you can try removing the border-t class from the parent of the workflow container and ensure hardware acceleration is enabled in your browser. For a code-level fix, consider experimenting with adding shape-rendering="geometricPrecision" or will-change="transform" to the SVG path elements in CustomEdge and CustomConnectionLine, or rounding coordinates before passing them to getBezierPath, though these changes would require frontend code edits [[source](https://github.com/langgenius/dify/blob/93a85ae98a1c1b8b27bda60d505441300b4bcbff/web/app/components/workflow/custom-edge.tsx#L8-L172)]. If you need more detailed steps for any of these suggestions, let me know! <!-- 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/ef77456a-6e6e-45c5-a65e-0cc3cf32316a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ef77456a-6e6e-45c5-a65e-0cc3cf32316a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ef77456a-6e6e-45c5-a65e-0cc3cf32316a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ef77456a-6e6e-45c5-a65e-0cc3cf32316a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ef77456a-6e6e-45c5-a65e-0cc3cf32316a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ef77456a-6e6e-45c5-a65e-0cc3cf32316a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ef77456a-6e6e-45c5-a65e-0cc3cf32316a?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20cable%20jitter%20on%204K%20screens%20is%20caused%20by%20how%20the%20Workflow%20Studio%20renders%20connector%20lines%20using%20SVG%20paths%20with%20floating-point%20coordinates%2C%20without%20any%20high-DPI-specific%20adjustments%20or%20coordinate%20rounding.%20This%20makes%20the%20cables%20visually%20unstable%20at%20high%20resolutions%2C%20while%20they%20appear%20stable%20at%201080P.%20There%20are%20no%20CSS%20properties%20like%20shape-rendering%20or%20will-change%20applied%20to%20the%20SVG%20elements%2C%20and%20no%20devicePixelRatio%20or%20scaling%20logic%20in%20the%20code%20to%20address%20this%20issue.%20%0A%0APerformance%20and%20jitter%20get%20much%20worse%20if%20browser%20hardware%20acceleration%20is%20disabled%2C%20because%20the%20browser%20creates%20extra%20compositing%20layers%E2%80%94especially%20if%20the%20parent%20of%20the%20workflow%20container%20uses%20the%20border-t%20class%20with%20overflow%3A%20hidden.%20Removing%20the%20border-t%20class%20from%20the%20parent%20div%20of%20the%20workflow%20container%20can%20dramatically%20improve%20performance%20and%20reduce%20jitter%20on%204K%20screens%2C%20increasing%20FPS%20and%20reducing%20composite%20layers%20from%2010%2B%20to%20just%201.%20This%20has%20been%20confirmed%20by%20community%20testing%20and%20browser%20dev%20tools%20profiling%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/29153%23issuecomment-3612918701%29%5D.%0A%0AThere%20are%20no%20built-in%20configuration%20flags%20or%20official%20workarounds%20in%20Dify%20for%20this%20issue.%20For%20now%2C%20you%20can%20try%20removing%20the%20border-t%20class%20from%20the%20parent%20of%20the%20workflow%20container%20and%20ensure%20hardware%20acceleration%20is%20enabled%20in%20your%20browser.%20For%20a%20code-level%20fix%2C%20consider%20experimenting%20with%20adding%20shape-rendering%3D%22geometricPrecision%22%20or%20will-change%3D%22transform%22%20to%20the%20SVG%20path%20elements%20in%20CustomEdge%20and%20CustomConnectionLine%2C%20or%20rounding%20coordinates%20before%20passing%20them%20to%20getBezierPath%2C%20though%20these%20changes%20would%20require%20frontend%20code%20edits%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/93a85ae98a1c1b8b27bda60d505441300b4bcbff/web/app/components/workflow/custom-edge.tsx%23L8-L172%29%5D.%0A%0AIf%20you%20need%20more%20detailed%20steps%20for%20any%20of%20these%20suggestions%2C%20let%20me%20know%21)&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/30553)
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#21437
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?