Search Issue Tracker
Fixed
Fixed in 6000.0.58f1, 6000.2.4f1, 6000.3.0b2, 6000.4.0a1
Votes
0
Found in
2022.3.40f1
6000.0.14f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-77345
Regression
No
UI Toolkit Debugger's box model does not display the content after the point.
Steps to reproduce:
- Open a Unity project
- Open the UI Toolkit Debugger via Window > UI Toolkit > Debugger
- In the 'Select a panel' dropdown, select InspectorWindow
- Click on the first element that displays in the list(EditorPanelRootElement)
- In the layout, try to replace any of the 0's with a 1
Actual results: The 1 can not be inputted and becomes a 0
Expected results: The 1 can be inputted and replaces the 0
Reproducible with versions:
- 6000.0.14f1 (Win 10)
- 2022.3.40f1 (Win 10)
- 2022.1.0a13 (Win 10)
- 2021.3.41f1 (Win 10)
Not reproducible with versions:
- 2022.1.0a12 (Win 10)
- Any version (Win 11)
- Any version (Mac Silicon)
Can’t test with versions: -
Tested on (OS): Windows 10, Windows 11, Mac Silicon
Notes:
- Bug appears to be limited to Windows 10
- The numbers 1, 5 and 9 are all affected. When trying to input those numbers into the Layout dimensions, they change to another number
** 1 -> 0
** 5 -> 4
* 9 -> 8
This can affect numbers in the middle of the sequence as well, not just at the start, however it depends on what numbers have already been inputted beforehand. If the only numbers inputted beforehand are affected numbers, then the subsequent numbers will be affected as well
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thanks for the report. While not ideal, and more indicators would help, this is actually expected behavior. The reason the numbers change right after being entered is due to rounding. UI Toolkit element size calculations include several scaling factors like Unity Editor scaling and Windows OS UI scaling/dpi. And even though element dimensions are in integer "pixels", they are actually floating point "points" underneath, which then get rounded by the debugger UI.