Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.4.0b9
6000.5.0a7
Issue ID
UUM-135892
Regression
Yes
The name of custom VisualElements is not shown in UI Builder when UxmlFactory is used
How to reproduce:
1. Open the attached project “IN-135458”
2. In the Project window, open the “Assets/UI Toolkit/UIDoc” asset
3. In the UI Builder hierarchy, select “NegativeCircleElement”
4. Press ‘F2’ on your keyboard, enter “test”, then press ‘Enter'
5. Observe the name shown in the Hierarchy
6. Save the file
7. Observe the name shown in the Hierarchy again
Actual result: The given name is not shown
Expected result: The given name is shown
Reproducible with: 6000.4.0a2 (417aa67423b3), 6000.4.0b10, 6000.5.0a7
Not reproducible with: 6000.0.68f1, 6000.3.10f1, 6000.4.0a1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Workaround: Changing the custom VisualElement to use “UxmlElementAttribute”
Notes:
- Element gets renamed successfully, however the name is not shown in the Hierarchy
- Deprecation warnings are shown in the Console for the affected VisualElement starting with 6000.4.0a1
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
- Search Default option for Column Format does not reset the column's format
- New Hierarchy filtering query block remains visible but filtering is not applied when returning from Prefab Mode in Context
- Empty scrollable space appears and scrollbar shrinks when scrolling down in the Tile Palette Brush Picks overlay window and List View selected with many saved brushes
- Player GameObject can’t be selected in the Hierarchy window during Step 4 of the "Get Started" tutorial in 2D Platformer Microgame because Hierarchy window is masked
- Gradient marker colors are removed when undoing marker movement in the Inspector Gradient field
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.