Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2020.2.3f1
2020.3
2021.1.0b2
2021.1.9f1
2021.2.0a1
Issue ID
1339759
Regression
Yes
Controls in the UI Debugger overlap when inspecting an element that has a label with null value
How to reproduce:
1. Open the user's attached project
2. Open the SampleScene
3. Select Window > UI Toolkit > Debugger
4. In the Hierarchy select 'ExampleGameObject'
5. In the UI Toolkit Debugger window select 'Pick Element'
6. Select the Example Component (Script) in the Inspector
7. In the UI Toolkit Debugger find 'VisualElement #exampleContainer'
8. Select one of the example labels
9. Observe the UI Toolkit Debugger
Expected result: Controls don't overlap
Actual result: Controls overlap
Reproducible with: 2020.2.3f1, 2020.2.7f1, 2020.3.13f1, 2021.1.0b2, 2021.1.13f1, 2021.2.0a1, 2021.2.0b1
Not reproducible with: 2019.4.28f1, 2020.2.2f1, 2021.1.0b1
Cannot test with: 2018.4.36f1 (due to errors)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a7
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b12
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.26f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.21f1