Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.5f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-132363
Regression
No
UITK Debugger new Classes element is not created with no information or warnings thrown when adding more than one element with the default name
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open UI Toolkit Debugger (Window > UI Toolkit > Debugger)
- Click on the "Select a panel" dropdown and select "HierarchyWindow"
- Open the "EditorPanelRootElement" foldout
- Open the "VisualElement" foldout
- Select the "Toolbar" element
- Open the "Classes" foldout
- Add a new element by pressing the "+" button
- Repeat step 8
- Observe the Classes list
Actual results: Second element is not added and no information or warnings are thrown
Expected results: Either an informational dialog or a warning is thrown, or the second class is created with an iterated name (for example newStyle 1)
Reproducible with versions: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Tested on (OS): MacOS Silicon Tahoe 26.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
- "DebugAllocatorMode" option changes when changed in another Editor instance
Add comment