Search Issue Tracker
Fixed
Fixed in 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Votes
0
Found in
6000.0.37f1
6000.1.0b4
6000.2.0a2
7000.0.0a1
Issue ID
UUM-97010
Regression
Yes
UI Builder Inspector shows element's custom name when using "Unset" to clear the name
Steps to reproduce:
1. Create a new project
2. Create and open a new UI Document (Assets → Create → UI Toolkit → UI Document)
3. Add a “VisualElement” to the UI Builder Hierarchy
4. Click on the “VisualElement” to open the UI Builder Inspector
5. At the very top under the element's name, input any text and press Enter
6. Observe that the name in the UI Builder Hierarchy is changed
7. Right click on the element’s name in the UI Builder Inspector and click "Unset"
8. Click away from the Inspector and then click on the element again to see it's UI Builder Inspector
9. Observe the element’s name
Expected result: The input field is empty
Actual result: The input field has the previously unset text in it
Reproducible in: 2023.2.0a18, 6000.0.37f1, 6000.1.0b4, 6000.2.0a2
Not reproducible in: 2022.3.57f1, 2023.2.0a17
Reproducible on: Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment