[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Describe the bug
The ELK integration in draw.io appears to not function properly. When trying to use ELK for layouts, no layout is applied, and the diagrams do not adjust as expected.
To Reproduce
Steps to reproduce the behavior:
Open draw.io.
Attempt to use the ELK layout engine for diagram organization.
No layout is applied, and no error message is shown.
The diagram remains in its original state without adjustment.
Expected behavior
The diagrams should automatically adjust their layout according to the ELK engine when selected. This was functioning previously but now appears broken.
Screenshots
N/A
draw.io version (In the Help->About menu of the draw.io editor):
draw.io version: v24.7.17
Desktop (please complete the following information):
OS: Linux Mint 22
Browser: Firefox
Browser Version: 130.0.1
Smartphone (please complete the following information if applicable):
Device: N/A
OS: N/A
Browser: N/A
Version: N/A
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
yes
Additional context
This issue has been reported before in issue #3634 but seems to have resurfaced.
Preflight Checklist
Describe the bug The ELK integration in draw.io appears to not function properly. When trying to use ELK for layouts, no layout is applied, and the diagrams do not adjust as expected.
To Reproduce Steps to reproduce the behavior:
Expected behavior The diagrams should automatically adjust their layout according to the ELK engine when selected. This was functioning previously but now appears broken.
Screenshots N/A
draw.io version (In the Help->About menu of the draw.io editor):
Desktop (please complete the following information):
Smartphone (please complete the following information if applicable):
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
Additional context This issue has been reported before in issue #3634 but seems to have resurfaced.
Can be checked with this