You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.
You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should report bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
The keyboard shortcut to toggle enabling/disabling the grid does not work to re-enable the grid, and seems to break some internal state related to the grid.
To Reproduce
Steps to reproduce the behavior:
Create a new blank diagram.
Press Ctrl + Shift + G to disable the grid.
Note that the appears to disappear (it is no longer rendered), but the grid checkbox is still checked under the Diagram tab in the right sidebar, and it is still checked in the View menu.
Press Ctrl + Shift + G to attempt to re-enable the grid. Note that the grid does not re-appear.
Try to get the grid to re-appear by unchecking and re-checking the "Grid" box in the Diagram tab in the right sidebar. Note that unchecking and re-checking the box does not change anything and that the internal rendering state of the grid now appears to be disconnected from the UI.
Try to get the grid to re-appear by selecting View > Grid from the menu bar. Note that the grid does not re-appear and the state of the Grid always shows as enabled (checked) in the dropdown menu regardless of how many times the menu item is clicked.
Note that from (5) and (6), the internal rendering state of the grid now appears to be disconnected from the UI and the internal grid state is broken.
Expected behavior
I would expect using the keyboard shortcut a second time would re-enable the grid and not break the grid rendering.
Screenshots
draw.io.grid.issue.mp4
draw.io version (In the Help->About menu of the draw.io editor):
draw.io version 26.0.2
Desktop (please complete the following information):
OS: Windows 10 Enterprise 22H2
Browser: Google Chrome Version 131.0.6778.205 (Official Build) (64-bit)
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
Yes
Additional context
As a workaround, picking a new color from the grid color picker in the right-hand sidebar seems to redraw the grid, but using the keyboard shortcut or the View > Grid menu item after breaks the grid functionality once again.
The text was updated successfully, but these errors were encountered:
Preflight Checklist
You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should report bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
The keyboard shortcut to toggle enabling/disabling the grid does not work to re-enable the grid, and seems to break some internal state related to the grid.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect using the keyboard shortcut a second time would re-enable the grid and not break the grid rendering.
Screenshots
draw.io.grid.issue.mp4
draw.io version (In the Help->About menu of the draw.io editor):
Desktop (please complete the following information):
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
Additional context
As a workaround, picking a new color from the grid color picker in the right-hand sidebar seems to redraw the grid, but using the keyboard shortcut or the View > Grid menu item after breaks the grid functionality once again.
The text was updated successfully, but these errors were encountered: