Search Issue Tracker
Fixed in 2022.2.21f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a16
Votes
0
Found in
2022.2.18f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-34955
Regression
Yes
UI Toolkit Debugger will not change the units of measurement to px when entering value without specified units for the first time
Reproduction steps:
1. Open the attached project “UIDebuggerBug“
2. Open the Package Manager (Window>Package Manager)
3. Select the Unity Registry tab
4. Select the 2D package
5. Open the UI Toolkit Debugger (Ctrl+F5)
6. Press the button Pick Element
7. Press on the Release element (below the 2D package title)
8. Replace any value that is set to “auto” with a numeric value
Expected result: The numeric value is applied, the “px” measurement is added
Actual result: “auto” value is reassigned
Reproducible with: 2022.2.0a15, 2022.2.18f1, 2023.1.0b16, 2023.2.0a14
Not reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.0a14
Reproducible on: Windows 11
Note: In Unity 2023.2.0a9 and above the size measurements cannot be changed unless the measurement is specified
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The cogwheel button in the Build History window gets distorted when the Build History window is resized or options are ticked in the toolbar
- Unity Hub (Arm64) fails to start when installed on Windows 11 (Arm64)
- “This version of Unity is not currently available for use with Build Automation” warning is shown only after setting up Cloud and Version Control warnings when adding Build Automation to a Build Profile
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
Add comment