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 reporting 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
When you change units to mm and start changing table cell size - the result is incorrect
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 reporting 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
When you change units to mm and start changing table cell size - the result is incorrect
To Reproduce
Steps to reproduce the behavior:
60pt
)View - Units - Millimeters
, see screeshot 2 - the width input now has a value of15.2mm
)Arrange
tab by clicking buttons next to the input3.8mm
)Expected behavior
The table cell size is properly changed
Screenshots
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):
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: